-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gatsby error on c9.io :: npm EPEERINVALID history #180
Comments
I think this issue was resolved by this PR by @scottnonnenberg a few days ago. Which version of Gatsby are you on? Try installing the latest by running |
I have the same problem as the one reported in the issue.
The problem happened right after doing a clean install today using Problems happens both when using node v0.12.7 and v4.4.0. No problem with node v5.1.0. |
done for default, blog and documentation starters :) |
Awesome thanks @mef! I'll close this as it seems like the issue is solved. |
You're welcome. In the mean time I found another dependency problem in the default starter, will have a look at it (the two other ones work well now). |
+1 On Thu, Mar 24, 2016 at 3:11 PM Mehdi El Fadil [email protected]
|
let me know how else i can help
zipped and attached is my terminal.log and my npm-debug.log
'npm install -g gatsby' warnings
'gatsby new my-site-title' error
workspace/test 'gatsby develop' errors
[248] /home/ubuntu/.nvm/versions/node/v4.3.2/lib/~/gatsby/~/history/lib/DOMStateStorage.js 2.15 kB {0} [built] [1 error]
The text was updated successfully, but these errors were encountered: