Error: It appears like Gatsby is misconfigured. on Fresh installs
See original GitHub issueDescription
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.
Steps to reproduce
gatsby new test
cd test
gatsby develop
Expected result
The site should start up with no errors
Actual result
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.
Environment
System: OS: macOS 10.14.6 CPU: (8) x64 Intel® Core™ 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
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Troubleshooting Common Errors - Gatsby
A likely problem is that the operating system you are running locally is different than the one where your site is deployed. Oftentimes...
Read more >[v2] Development broken -> JSONStore error #7642 - GitHub
Uncaught Error : It appears like Gatsby is misconfigured. JSONStore is Gatsby internal development-only component and should never be used in ...
Read more >I am getting error when run gatsby project - Stack Overflow
Just run npm install gatsby-plugin-sharp if you are using the plugin in your gatsby-config.js file. Delete your package-lock.json, your cache ( ...
Read more >gatsby-plugin-typegen - npm
Gatsby plugin to play with extream type-safety. Latest version: 3.1.0, last published: a month ago. Start using gatsby-plugin-typegen in ...
Read more >Troubleshooting Preview Problems - Forestry.io
If your build command looks correct, it's possible that your build is still throwing an error. Errors in your template code, or missing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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?
^ 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 👍