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
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 am facing issue in installing dashing-js in centos , i have followed the following steps , but i am getting the below error.[root#ip-10-0-2-15 vagrant]# npm install -g node-dashing-js
npm WARN deprecated jade#0.35.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
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 node-uuid#1.4.7: use uuid module instead
/usr/bin/dashing-js -> /usr/lib/node_modules/node-dashing-js/bin/dashing-js
/usr/lib
└─┬ node-dashing-js#1.0.3
└─┬ node-sass#3.3.3
├─┬ meow#3.7.0
│ └── normalize-package-data#2.3.6
└─┬ node-gyp#3.5.0
└── fstream#1.0.11
[root#ip-10-0-2-15 vagrant]# dashing-js new sweet_dashboard_project
: No such file or directory
Make sure you have npm global bin path included in your PATH.
Check PATh and where dashing-js is installed by
echo $PATH
which dashing-js
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.
i tried to clean the cache and install it again but it says a warning unmet dependency
C:\Users\Ralph>npm cache clean
C:\Users\Ralph>npm install -g cordova
C:\Users\Ralph\AppData\Roaming\npm\cordova -> C:\Users\Ralph\AppData\Roaming\npm
\node_modules\cordova\bin\cordova
npm WARN unmet dependency C:\Users\Ralph\AppData\Roaming\npm\node_modules\phoneg
ap\node_modules\connect-phonegap requires shelljs#'0.2.6' but will load
npm WARN unmet dependency C:\Users\Ralph\AppData\Roaming\npm\node_modules\phoneg
ap\node_modules\shelljs,
npm WARN unmet dependency which is version 0.1.4
npm WARN unmet dependency C:\Users\Ralph\AppData\Roaming\npm\node_modules\phoneg
ap\node_modules\cordova\node_modules\plugman requires request#'2.22.0' but will
load
npm WARN unmet dependency C:\Users\Ralph\AppData\Roaming\npm\node_modules\phoneg
ap\node_modules\cordova\node_modules\request,
npm WARN unmet dependency which is version 2.21.0
cordova#4.2.0 C:\Users\Ralph\AppData\Roaming\npm\node_modules\cordova
├── underscore#1.7.0
├── q#1.0.1
├── nopt#3.0.1 (abbrev#1.0.5)
└── cordova-lib#4.2.0 (valid-identifier#0.0.1, osenv#0.1.0, properties-parser#0.
2.3, bplist-parser#0.0.6, mime#1.2.11, unorm#1.3.3, semver#2.0.11, shelljs#0.3.0
, rc#0.5.2, dep-graph#1.1.0, npm#1.4.28, elementtree#0.1.5, xcode#0.6.7, through
2#0.6.3, npmconf#0.1.16, glob#4.0.6, plist#1.1.0, tar#1.0.2, request#2.47.0, d8#
0.4.4, cordova-js#3.7.3)
thank you in advance
Cordova cannot run on the latest version of Node because it actually requires v10.x of Node. So, here is how I avoided the "Warning: unmet dependency" when installing Cordova:
> npm uninstall -g cordova
Use n (nvm for Windows) to downgrade an older version of Node (Windows users will need to downgrade and use):
> n 0.10.40
> npm cache clean
> npm install -g cordova
If you want to install Ionic, then in step 4, call the npm command to directly install ionic (with no #latest) instead of cordova, like this:
> npm install -g ionic
Note: Linux / OSX users may need to prepend the npm commands with "sudo".
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.