I can no longer run gatsby develop without getting this error
Error: It appears like Gatsby is misconfigured. JSONStore is Gatsby internal development-only component and should never be used in production.
Unless your site has a complex or custom webpack/Gatsby configuration this is likely a bug in Gatsby. Please report this at https://github.com/gatsbyjs/gatsby/issues with steps to reproduce this error.
this happens on existing and new sites
I have deleted cache and re-downloaded the node_modules.
I have created new sites with just react, react-dom, and gatsby, but I still get this error.
gatsby new testcd testgatsby developThe site should start up with no errors
I get an error
Error: It appears like Gatsby is misconfigured. JSONStore is Gatsby internal development-only component and should never be used in production.
Unless your site has a complex or custom webpack/Gatsby configuration this is likely a bug in Gatsby. Please report this at https://github.com/gatsbyjs/gatsby/issues with steps to reproduce this error.
System:
OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Shell: 5.3 - /bin/zsh
Binaries:
Node: 13.7.0 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.6 - /usr/local/bin/npm
Languages:
Python: 2.7.16 - /usr/bin/python
Browsers:
Chrome: 78.0.3904.108
Firefox: 69.0.2
Safari: 13.0.5
npmPackages:
gatsby: ^2.19.7 => 2.19.7
npmGlobalPackages:
gatsby-cli: 2.7.30
I got it to work with hello-world not sure. why nothing else is working
Did you delete any of the gatsby-*.js files? Specifically, if you have any Gatsby plugins included, a gatsby-config.js is requried. If you are trying to build pages at build time, you need a gatsby-node.js.
I'm getting this all of a sudden also didn't change anything with gatsby config all up to date with all dependencies.
^ turns out I had run export NODE_ENV=production in the same terminal window before so I changed it back to development all good nvm 馃憤
Thank you for opening this!
This seems like environment issues on your systems and not so much like a bug in Gatsby. Make sure that nothing e.g. changes your NODE_ENV as Gatsby accesses this for e.g. webpack.
We're marking this issue as answered and closing it for now but please feel free to comment here if you would like to continue this discussion. We also recommend heading over to our communities if you have questions that are not bug reports or feature requests. We hope we managed to help and thank you for using Gatsby!
Had the same issue with the same root cause. Might be worth updating the error message to note that it can be caused by NODE_ENV?
I'm having this problem right now.
Most helpful comment
Had the same issue with the same root cause. Might be worth updating the error message to note that it can be caused by NODE_ENV?