gatsby: [gatsby-plugin-netlify-cms]: Breaks Gatsby `develop` and `build`
Hello 👋
I’ve noticed that by adding the latest gatsby-plugin-netlify-cms plugin, gatby develop and gatsby build stop working.
I’ve done a few tests and isolated the issue down to this plugin. If I remove it, everything works again.
Below are the errors I’m getting:
gatsby develop

gatsby build

package.json

I’ve tried downgrading the version of all packages, but not luck. The only way to get my build to work again is by removing gatsby-plugin-netlify-cms.
Appreciate any guidance, thanks! 👍
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 26 (14 by maintainers)
Commits related to this issue
- exclude Netlify CMS styles in build-css phase (#3895) — committed to gatsbyjs/gatsby by erquhart 6 years ago
That won’t be necessary, I’m working on a fix for this right now. Stay tuned.
@peduarte If you are using yarn, you can use this in your
package.json:…and then delete your
yarn.lockandnode_modulesto be sureAlright I think I know what’s going on, I’ll take a swing at it in the morning.
Thanks for having a look, I hope this will be resolved soon. Should we reopen the issue or create a new one ?
I just started a new project using ‘gatsby-plugin-netlify-cms’, and I’m still not able to build my CSS Module if the plugin is active, ‘gatsby develop’ works fine ‘gatsby build’ output an error :
Error: /Users/Tom/Developer/GitHub/wise-starter/node_modules/extract-text-webpack-plugin/loader.js?{"omit":1,"extract":true,"r emove":true}!/Users/Tom/Developer/GitHub/wise-starter/node_modules/style-loader/index.js!/Users/Tom/Developer/GitHub/wise-starter/node_modules/css-loader/index.js?modules&minimize&importLoa ders=1&localIdentName=[path]---[name]---[local]---[hash:base64: 5]!/Users/Tom/Developer/GitHub/wise-starter/node_modules/sass-loader/index.js?{"plugins":[]}!/Users/Tom/Developer/GitHub/wise- starter/src/components/header.module.sass doesn't export conten tThe only way to get my build to work is by removing gatsby-plugin-netlify-cms.
Beautiful, great work everyone 🎉
@peduarte you may have to
yarn upgrade gatsby-plugin-netlify-cms, it updates the sub dependencies.@Jaikant If you think it is an error in Netlify CMS, please report the issue in Netlify CMS Github.
Hi, this is known error in recently released netlify-cms 1.2.0, see this issue: https://github.com/netlify/netlify-cms/issues/1097