react-bootstrap#0.26.4 depends on react#^0.13.3 but react#0.14.3 gets installed as a dependency. It also installs react#0.13.3 in the top level of node_modules (which is weird but fine). The 0.14.3 version breaks my application.
I expect only react#0.13.3 to be installed and not in the top level but in node_modules/react-bootstrap/node_modules/react
Why do I get react#0.14.3?
I have also tried adding react#0.13.3 in peerDependencies but I still get 0.14.3. I have also tried using npm 3, but doing a clean npm install for the app I'm building with npm 3 takes 75 minutes, so I'm hoping that there is a way to install react-bootstrap with npm 2.
kullervo: ~/tmp
$ mkdir test-react-bootstrap
kullervo: ~/tmp
$ cd test-react-bootstrap
kullervo: ~/tmp/test-react-bootstrap
$ npm install react-bootstrap#0.26.4
npm WARN peerDependencies The peer dependency react#^0.13 included from react-bootstrap 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 react#>=0.11.0 included from uncontrollable 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 react#>=0.13.0 included from react-overlays 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.
react#0.13.3 node_modules/react
└── envify#3.4.0 (through#2.3.8, jstransform#10.1.0)
react-bootstrap#0.26.4 node_modules/react-bootstrap
├── classnames#2.2.1
├── keycode#2.1.0
├── dom-helpers#2.4.0
├── lodash-compat#3.10.1
├── react-prop-types#0.3.0 (warning#2.1.0)
├── babel-runtime#5.8.34 (core-js#1.2.6)
├── react#0.14.3 (envify#3.4.0, fbjs#0.3.2)
├── react-overlays#0.4.4 (react-prop-types#0.2.2, warning#2.1.0)
└── uncontrollable#3.2.0 (invariant#2.2.0)
kullervo: ~/tmp/test-react-bootstrap
$ grep version node_modules/react-bootstrap/package.json | head -n 1
"version": "0.26.4",
kullervo: ~/tmp/test-react-bootstrap
$ grep version node_modules/react-bootstrap/node_modules/react/package.json | head -n 1
"version": "0.14.3",
kullervo: ~/tmp/test-react-bootstrap
$ grep version node_modules/react/package.json | head -n 1
"version": "0.13.3",
kullervo: ~/tmp/test-react-bootstrap
$ node -v
v0.12.9
kullervo: ~/tmp/test-react-bootstrap
$ npm -v
2.14.9
Seems like npm 2 is just plain broken. By upgrading all my app's deps, I was able to use latest version of node and npm, and suddenly the performance is good. Case closed. Lesson learned: Don't use npm 2.
Related
Im working with AWS-Amplify and just updated it's CLI to the latest version, and now NPM complains that there are unmet dependencies, though graphql is clearly installed at the right version. What am missing here? Thanks for any clarification!
$ npm list -g --depth 0
/usr/local/lib
├── #aws-amplify/cli#4.12.0
├── #vue/cli#4.0.5
├── browser-sync#2.26.7
├── firebase-tools#7.10.0
├── graphql#14.5.8
├── nodemon#2.0.2
├── npm#6.13.6
└── parcel-bundler#1.12.4
npm ERR! peer dep missing: graphql#^14.5.8, required by #graphql-toolkit/file-loading#0.9.0
npm ERR! peer dep missing: graphql#^14.2.0, required by relay-compiler#6.0.0
This happens when your node version is not latest or when the dependencies require a certain version of other npm. Just check if all the npm packages and node is of latest version.
I wanted to check all my globally installed packages and ran npm list -g --depth 0. I would like to uninstall some packages, for example prop-types and get rid of the error I get with 2 of them.
I want to uninstall prop-types. I did it with npm uninstall -g prop-types but it doesn't work. Also tried npm uninstall -g prop-types --save
~ npm list -g --depth 0
/usr/local/lib
├── create-react-app#1.5.2
├── gatsby-cli#2.4.11
├── gitmoji-cli#1.9.2
├── json-server#0.14.2
├── mern-cli#2.5.0
├── nodemon#1.18.6
├── npm#6.9.2
└── strapi#3.0.0-alpha.24.1
npm ERR! peer dep missing: prop-types#^15.6.0, required by react-ga#2.5.7
npm ERR! peer dep missing: react#^15.6.2 || ^16.0, required by react-ga#2.5.7
And what about this react-ga ? It's not listed, but it looks like it needs some packages. How can I uninstall it if it's already installed? This is what I get when I try to uninstall it :
~ npm uninstall react-ga
npm WARN saveError ENOENT: no such file or directory, open '/Users/philippe/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/Users/philippe/package.json'
npm WARN philippe No description
npm WARN philippe No repository field.
npm WARN philippe No README data
npm WARN philippe No license field.
audited 1 package in 0.62s
found 0 vulnerabilities
To get rid of the peer dep missing error, you must remove the #gatsby-cli package
npm uninstall -g gatsby-cli
I am having problem while using Yeoman, I have updated node to 6.2, but still having problem with generating scaffold. It seem that fsevents#1.0.12 is not compatible with my architecture. what can I do ?
This is the output
$ yo webapp
_-----_
| | .--------------------------.
|--(o)--| | 'Allo 'allo! Out of the |
`---------´ | box I include HTML5 |
( _´U`_ ) | Boilerplate, jQuery, and |
/___A___\ | a gulpfile to build your |
| ~ | | app. |
__'.___.'__ '--------------------------'
´ ` |° ´ Y `
? What more would you like? (Press <space> to select)Sass, Bootstrap, Modernizr
? Choose your style of DSL BDD
create bower.json
create package.json
create gulpfile.js
identical .babelrc
identical .gitignore
identical .gitattributes
identical .bowerrc
identical .editorconfig
create app/favicon.ico
create app/apple-touch-icon.png
create app/robots.txt
create app/styles/main.scss
create app/scripts/main.js
create app/index.html
create test/spec/test.js
create test/index.html
I'm all done. Running npm install & bower install for you to install the required dependencies. If this fails, try running the command yourself.
npm WARN deprecated graceful-fs#3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated lodash#1.0.2: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated cross-spawn-async#2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated graceful-fs#2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global node-gyp#3.3.1 should be installed with -g
> node-sass#3.7.0 install /home/theo/Lin/webapp/node_modules/node-sass
> node scripts/install.js
Binary downloaded and installed at /home/theo/Lin/webapp/node_modules/node-sass/vendor/linux-x64-46/binding.node
> node-sass#3.7.0 postinstall /home/theo/Lin/webapp/node_modules/node-sass
> node scripts/build.js
"/home/theo/Lin/webapp/node_modules/node-sass/vendor/linux-x64-46/binding.node" exists.
testing binary.
Binary is fine; exiting.
> optipng-bin#3.1.2 postinstall /home/theo/Lin/webapp/node_modules/optipng-bin
> node lib/install.js
✔ optipng pre-build test passed successfully
> jpegtran-bin#3.0.6 postinstall /home/theo/Lin/webapp/node_modules/jpegtran-bin
> node lib/install.js
✔ jpegtran pre-build test passed successfully
> gifsicle#3.0.3 postinstall /home/theo/Lin/webapp/node_modules/gifsicle
> node lib/install.js
✔ gifsicle pre-build test passed successfully
/home/theo/Lin/webapp
├─┬ babel-core#6.9.0
│ ├─┬ babel-code-frame#6.8.0
│ │ ├── esutils#2.0.2
│ │ └── js-tokens#1.0.3
│ ├─┬ babel-generator#6.9.0
........................
........................
├── glob#4.5.3
├── lodash#2.4.2
├── propprop#0.3.0
└─┬ through2#0.6.5
└─┬ readable-stream#1.0.34
└── isarray#0.0.1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.12
Fsevents is an optional dependency for Mac OSX. You don't need to worry about it.
https://www.npmjs.com/package/fsevents
Hello I recently tried installing grunt-command line interface according to the instructions on their website using the node package manager command
sudo npm install -g grunt-cli
It didnt work and I got the following errors
/usr/local/bin/grunt -> /usr/local/lib/node_modules/grunt-cli/bin/grunt
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/couch-login requires request#'~2.9.202' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/request,
npm WARN unmet dependency which is version 2.30.0
grunt-cli#0.1.13 /usr/local/lib/node_modules/grunt-cli
├── resolve#0.3.1
├── nopt#1.0.10 (abbrev#1.0.5)
└── findup-sync#0.1.3 (lodash#2.4.1, glob#3.2.11)
➜ ~
I'm not sure how i update this dependancy. Can anyone shed any light on this?
Try the following:
npm cache clean
npm install -g npm (update npm)
reinstall node.js completely (if all fails).
Please let me know if this works.
I installed coffee-script as per directions.
$ npm install http://github.com/jashkenas/coffee-script/tarball/master
npm http GET http://github.com/jashkenas/coffee-script/tarball/master
npm http 200 http://github.com/jashkenas/coffee-script/tarball/master
npm http GET https://registry.npmjs.org/mkdirp
npm http 200 https://registry.npmjs.org/mkdirp
npm WARN package.json cookie-signature#1.0.0 No repository field.
npm WARN package.json fresh#0.1.0 No repository field.
npm WARN package.json methods#0.0.1 No repository field.
npm WARN package.json range-parser#0.0.4 No repository field.
npm WARN package.json send#0.1.0 No repository field.
npm WARN package.json ms#0.1.0 No repository field.
npm WARN package.json pause#0.0.1 No repository field.
npm WARN package.json bytes#0.2.0 No repository field.
npm WARN package.json formidable#1.0.11 No repository field.
npm WARN package.json css#1.0.8 No repository field.
npm WARN package.json uglify-js#2.2.5 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json walk#2.2.1 No repository field.
npm WARN package.json css-parse#1.0.4 No repository field.
npm WARN package.json css-stringify#1.0.5 No repository field.
coffee-script#1.6.3 node_modules/coffee-script
└── mkdirp#0.3.5
yet when i execute 'coffee' command i get
$ coffee
-bash: coffee: command not found
What am i doing wrong?
PS: i am doing this on Mac Terminal
EDIT: -
Same problem is occurs when i install nodemon the npm install takes place similar to above. But when i input a nodemon command on $ prompt it says -bash: nodemon: command not found
I installed coffeescript on my mac yeasterday as a matter of fact. Here is how I did it:
First of all, go install NodeJS.
Then go in Terminal and type the following: sudo npm install -g coffee-script
That's it - If you type in coffee in Terminal, it should start without a problem
Anything you want to run as a command (nodemon, coffee, node-inspector) must be installed with npm install -g the-package-name. If you use npm install it just puts it into your local node_modules directory and won't create the symlink for command line execution.
If you find that you need to use sudo, you might want to read this blog post: http://howtonode.org/introduction-to-npm:
what, no sudo?
I strongly encourage you not to do package management
with sudo! Packages can run arbitrary scripts, which makes sudoing a
package manager command as safe as a chainsaw haircut. Sure, it's fast
and definitely going to cut through any obstacles, but you might
actually want that obstacle to stay there.
I recommend doing this once instead:
sudo chown -R $USER /usr/local