Skip to content
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

Closed
wommy opened this issue Mar 10, 2016 · 7 comments
Closed

gatsby error on c9.io :: npm EPEERINVALID history #180

wommy opened this issue Mar 10, 2016 · 7 comments

Comments

@wommy
Copy link

wommy commented Mar 10, 2016

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

npm WARN peerDependencies The peer dependency history@^1.12.1 || ^2.0.0 included from scroll-behavior will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN optional dep failed, continuing [email protected]
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN optional dep failed, continuing [email protected]
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.

'gatsby new my-site-title' error

[Error: npm WARN package.json [email protected] No repository field.
npm WARN peerDependencies The peer dependency eslint-plugin-react@^3.16.1 included from eslint-config-airbnb will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Linux 4.2.0-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v4.3.2/bin/node" "/home/ubuntu/.nvm/versions/node/v4.3.2/bin/npm" "install"
npm ERR! node v4.3.2
npm ERR! npm  v2.14.12
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package [email protected] does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants eslint-plugin-react@^3.16.1

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/test/npm-debug.log
]

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]

ERROR in /home/ubuntu/.nvm/versions/node/v4.3.2/lib/~/gatsby/~/history/lib/DOMStateStorage.js
Module not found: Error: Cannot resolve module 'warning' in /home/ubuntu/.nvm/versions/node/v4.3.2/lib/node_modules/gatsby/node_modules/history/lib
 @ /home/ubuntu/.nvm/versions/node/v4.3.2/lib/~/gatsby/~/history/lib/DOMStateStorage.js 10:15-33
@KyleAMathews
Copy link
Contributor

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 npm install -g gatsby

@mef
Copy link

mef commented Mar 24, 2016

I have the same problem as the one reported in the issue.

Which version of Gatsby are you on?

$ gatsby -V
0.8.11

Try installing the latest by running npm install -g gatsby

The problem happened right after doing a clean install today using npm install -g gatsby.

Problems happens both when using node v0.12.7 and v4.4.0.

No problem with node v5.1.0.

@KyleAMathews
Copy link
Contributor

Hmmm... looks like the problem is with NPM 2 as some of the starters have bad dependencies. @mef or @wommy if either of you could look at upgrading the starter dependencies so they work on NPM 2 and create a PR that'd be 💯

@mef
Copy link

mef commented Mar 24, 2016

done for default, blog and documentation starters :)

@KyleAMathews
Copy link
Contributor

Awesome thanks @mef!

I'll close this as it seems like the issue is solved.

@mef
Copy link

mef commented Mar 24, 2016

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).

@KyleAMathews
Copy link
Contributor

+1

On Thu, Mar 24, 2016 at 3:11 PM Mehdi El Fadil [email protected]
wrote:

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).


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#180 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants