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

npm install fails with package [email protected] does not satisfy peerDependencies requirements! #12

Closed
fuentesjr opened this issue Jun 22, 2016 · 2 comments

Comments

@fuentesjr
Copy link

fuentesjr commented Jun 22, 2016

sfuentes@sfuentes-desktop:~/Projects/myApp$ uname -a
Linux sfuentes-desktop 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
sfuentes@sfuentes-desktop:~/Projects$ node --version
v4.4.4
sfuentes@sfuentes-desktop:~/Projects$ npm version
{ npm: '2.15.1',
  ares: '1.10.1-DEV',
  http_parser: '2.5.2',
  modules: '46',
  node: '4.4.4',
  openssl: '1.0.2h',
  uv: '1.8.0',
  v8: '4.5.103.35',
  zlib: '1.2.8' }
sfuentes@sfuentes-desktop:~/Projects$ sudo npm install -g mern-cli
[sudo] password for sfuentes: 
/usr/local/bin/mern -> /usr/local/lib/node_modules/mern-cli/bin/mern.js
/usr/local/bin/merng -> /usr/local/lib/node_modules/mern-cli/bin/merng.js
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client/node_modules/npm-package-arg requires semver@'4' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/semver,
npm WARN unmet dependency which is version 5.1.0
[email protected] /usr/local/lib/node_modules/mern-cli
├── [email protected]
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected]
├── [email protected]
└── [email protected] ([email protected], [email protected], [email protected])
sfuentes@sfuentes-desktop:~/Projects$ mern init myApp
Initialized empty Git repository in /home/sfuentes/Projects/myApp/.git/
Fetching the boilerplate...⠋
From https://github.com/Hashnode/mern-starter
Completed.....You are good to go!
sfuentes@sfuentes-desktop:~/Projects$ cd myApp/
sfuentes@sfuentes-desktop:~/Projects/myApp$ npm install
npm WARN peerDependencies The peer dependency webpack@>=1.12.9 <3.0.0 included from babel-plugin-webpack-loaders 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 peerDependencies The peer dependency webpack@^1.4.0-beta6 included from chunk-manifest-webpack-plugin 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 peerDependencies The peer dependency webpack@^1.9.11 included from extract-text-webpack-plugin 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 deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN optional dep failed, continuing [email protected]
npm WARN optional dep failed, continuing [email protected]
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

> [email protected] postinstall /home/sfuentes/Projects/myApp/node_modules/pre-commit/node_modules/cross-spawn/node_modules/spawn-sync
> node postinstall


> [email protected] install /home/sfuentes/Projects/myApp/node_modules/pre-commit
> node install.js


> [email protected] postinstall /home/sfuentes/Projects/myApp/node_modules/mockgoose/node_modules/mongodb-prebuilt/node_modules/spawn-sync
> node postinstall

|
> [email protected] postinstall /home/sfuentes/Projects/myApp/node_modules/mockgoose/node_modules/mongodb-prebuilt
> node install.js

done
inside extract, run complete
Done installing MongoDB
npm WARN optional dep failed, continuing [email protected]
\
> [email protected] postinstall /home/sfuentes/Projects/myApp/node_modules/postcss-cssnext/node_modules/caniuse-api
> node generator.js

caniuse-api: Generation ok
-
> [email protected] install /home/sfuentes/Projects/myApp/node_modules/limax/node_modules/pinyin/node_modules/nodejieba
> node-gyp rebuild

make: Entering directory `/home/sfuentes/Projects/myApp/node_modules/limax/node_modules/pinyin/node_modules/nodejieba/build'
  CXX(target) Release/obj.target/nodejieba/lib/index.o
  CXX(target) Release/obj.target/nodejieba/lib/nodejieba.o
  SOLINK_MODULE(target) Release/obj.target/nodejieba.node
  COPY Release/nodejieba.node
make: Leaving directory `/home/sfuentes/Projects/myApp/node_modules/limax/node_modules/pinyin/node_modules/nodejieba/build'
npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1
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 webpack@1 || ^2.1.0-beta
npm ERR! peerinvalid Peer [email protected] wants webpack@^1.9.11
npm ERR! peerinvalid Peer [email protected] wants webpack@1 || ^2.1.0-beta
npm ERR! peerinvalid Peer [email protected] wants webpack@^1.4.0-beta6
npm ERR! peerinvalid Peer [email protected] wants webpack@>=1.12.9 <3.0.0
npm ERR! peerinvalid Peer [email protected] wants webpack@^2.1.0-beta

npm ERR! Please include the following file with any support request:
npm ERR!     /home/sfuentes/Projects/myApp/npm-debug.log
@somus
Copy link
Contributor

somus commented Jun 23, 2016

This problem will be fixed once you upgrade to npm 3. Upgrade by running npm install -g npm@next. Let me know whether it resolves your problem?

@fuentesjr
Copy link
Author

@somus Yup, that was the issue. Thank you sir. I'll go ahead and close this issue now. By the way, was this relatively obvious?

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

2 participants