DSchau / gatsby-blog-starter-kit

A simple starter kit for a static blog created with Gatsby
https://gatsby-blog-starter-kit.netlify.com/
MIT License
126 stars 39 forks source link

Project does not compile after creation #43

Closed garritfra closed 5 years ago

garritfra commented 5 years ago

After creating a project via gatsby new blog https://github.com/dschau/gatsby-blog-starter-kit and starting it with npm start, I get the following output:

► npm start

> gatsby-blog-starter-kit@1.2.0 start /Users/frankeg/dev/blog
> npm run develop

> gatsby-blog-starter-kit@1.2.0 develop /Users/frankeg/dev/blog
> gatsby develop

The above error occurred in the <StoreStateProvider> component:
    in StoreStateProvider
    in App

React will try to recreate this component tree from scratch using the error boundary you provided, App.
Warning: App: Error boundaries should implement getDerivedStateFromError(). In that method, return a state update to display an error message or fallback UI.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gatsby-blog-starter-kit@1.2.0 develop: `gatsby develop`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gatsby-blog-starter-kit@1.2.0 develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/frankeg/.npm/_logs/2019-11-01T22_03_47_665Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gatsby-blog-starter-kit@1.2.0 start: `npm run develop`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gatsby-blog-starter-kit@1.2.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/frankeg/.npm/_logs/2019-11-01T22_03_47_683Z-debug.log

I suppose this has to do with a new version of react, but cant exactly point out what it is. could you take a look at this?

DSchau commented 5 years ago

This isn’t an issue with the starter.

Did you use yarn to install dependencies?

DSchau commented 5 years ago

What seems to be happening is later versions than are pinned in yarn.lock are being installed.

garritfra commented 5 years ago

I used npm in this case. That's probably it. Closing this issue, thanks!