I am trying to install mongoose on a windows 7 machine by
npm install mongoose
but cant get it to work.
the error is:
kerberos.vcxproj -> D:\dan\revert\node_modules\mongoose\node_modules\mongodb\node_modules\mongodb-core\node_modules\kerberos\build\Release\\kerberos.node
> bson-ext#0.1.6 install D:\dan\revert\node_modules\mongoose\node_modules\mongodb\node_modules\mongodb-core\node_modules\bson\node_modules\bson-ext
> ./node_modules/node-pre-gyp/bin/node-pre-gyp.js install --fallback-to-build
'.' is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional dep failed, continuing bson-ext#0.1.6
npm ERR! peerinvalid The package mongoose does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer node-restful#0.1.18 wants mongoose#~3
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "mongoose"
npm ERR! cwd D:\dan\revert
npm ERR! node -v v0.10.34
npm ERR! npm -v 1.4.28
npm ERR! code EPEERINVALID
npm ERR! not ok code 0
I tried:
npm install -g node-gyp
npm uninstall mongodb --save
npm install mongoose --save
Any idea will be welcome
I would have left a comment, but I don't have enough reputation points.
I agree with #user645715, try a lower version of mongoose. Or install the latest node & npm. Look into Node Version Manager (NVM) for easy switching between versions of node.
On windows to get node-gyp to build you need to install Python 2.7 and have the visual studio build components. Just install Visual Studio Express. This is all in the node-gyp documentation:
https://www.npmjs.com/package/node-gyp
npm install --save mongoose#3.8.35
Related
Hi I'm unable to install the firebase tools via command prompt using admin mode and I am getting the error bellow:
F:\rnd\MyChat>npm install firebase
> grpc#1.8.4 install F:\rnd\MyChat\node_modules\grpc
> node-pre-gyp install --fallback-to-build --library=static_library
node-pre-gyp ERR! Tried to download(undefined): https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v1.8.4/node-v57-win32-x64-unknown.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for grpc#1.8.4 and node#8.9.3 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\Users\ani\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19)
gyp ERR! stack at PythonFinder.<anonymous>
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grpc#1.8.4 install: `node-pre-gyp install --fallback-to-build --library=static_library`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the grpc#1.8.4 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
you are trying to install firebase javascript library not the firebase-tools the node module for firebase tools is firebase-tools and firebase 3.16 version and along with that in the local folder npm install node-gyp
you should run
npm install -g firebase-tools
This is something that may work, try doing the following.
npm i -g firebase-tools
Finally my issue has been resolved by following these below steps
firstly i installed npm install node-gyp in my local folder and downgraded my firebase-tools version from 3.17 to 3.16 and Mainly i disabled my Anti Virus
below is the reference link for that
https://github.com/grpc/grpc-node/issues/121
If you are using a newer version of nodejs try uninstalling and using node-v10.15.3
https://nodejs.org/download/release/v10.15.3/
I want to install Mix in laravel . I run "npm install --no-bin-links" in my IDE terminal or in CMD but I get this error: (my laravel version is 5.4.27)
D:\wamp64\www\laravelProject>npm install --no-bin-links
npm WARN deprecated node-uuid#1.4.8: Use uuid module instead
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "D:\Program Files\nodejs\node.exe" "D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--no-bin-links"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! Maximum call stack size exceeded
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! D:\wamp64\www\laravelProject\npm-debug.log
I found!!
I remove node-modules then removed package-lock.json and ran
The following command helped me too:
npm cache clean --force
Also, you might need to add sudo in linux.
Sails.js will not install, but just to make sure npm is working I installed grunt
npm install -g grunt-cli and it installed correctly.
But when I run npm install -g sails I get an error.
Command prompt error:
`sails#0.11.0 preinstall C:\Users\User\AppData\Roaming\npm\node_modules\sails
node ./lib/preinstall_npmcheck.js
Sails.js Installation - Error
Unable to check your npm-version
Please reinstall npm to use Sails.js
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-
cli.js" "-g" "install" "sails"
npm ERR! node v4.0.0
npm ERR! npm v2.14.2
npm ERR! code ELIFECYCLE
npm ERR! sails#0.11.0 preinstall: node ./lib/preinstall_npmcheck.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sails#0.11.0 preinstall script 'node ./lib/preinstall_npmcheck.js'.
npm ERR! This is most likely a problem with the sails package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./lib/preinstall_npmcheck.js
npm ERR! You can get their info via:
npm ERR! npm owner ls sails
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Windows\system32\npm-debug.log`
npm-debug.log:
https://gist.github.com/anonymous/c850ac8c71e0410db020
I got the same errors.
npm -g install sails
But it worked when I ran command line as administrator.
I solved this by running npm install -g sails --ignore-scripts.
The only thing I can think of is for some reason I don't have ./lib/preinstall_npmcheck.js file and it is trying to run it, so by ignoring it I don't get the error, hence the successful install.
I still don't understand why, but I hope this helps someone.
UPDATE: SOLVED like this:
1.Like #salem said, I had to install contextify:
npm install contextify
then sudo npm install -g topojson threw an error about needing to accept an Xcode license agreement. It threw the command I needed too, so I ran that, then tried sudo npm install -g topojson again, and it worked!
Problem:
So, I'm getting errors aplenty with:
sudo npm install -g topojson
I haven't found solution in other threads.
Is Xcode right? I have Xcode 4.6.2 -- and update gives this error: "Xcode [5] can’t be installed on “Macintosh HD” because Mac OS X version 10.8.4 or later is required."
node & npm seem ok … they both spit out some help at node --help and npm --help
2a. I've tried deleting then reinstalling node using node-v0.10.24-darwin-x86.tar. Though I'm very unclear on what any of this is.
This is the end of the log:
npm ERR! Failed at the contextify#0.1.6 install script.
npm ERR! This is most likely a problem with the contextify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls contextify
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 11.4.2
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "topojson"
npm ERR! cwd /Users/maggielee/Downloads
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/maggielee/Downloads/npm-debug.log
npm ERR! not ok code 0
The whole log is here: http://greencracker.net/wp-content/uploads/2013/12/error.txt
What do you think?
I'm a recent convert to Mac from Windows, and currently just trying to get my tools setup.
I first installed node using homebrew, which was giving me errors (same as what I still have). I later removed node using homebrew and installed using the pkg from the node website.
I can access node in the command line and npm. The problem is when I try to install modules on the project locally I get something like:
npm install grunt-contrib
Error extracting archive { [Error: ENOENT, open '/Users/davidmckeown/dev/adt-com/node_modules/grunt-contrib/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/tmp/phantomjs-1.7.0-macosx.zip']
errno: 34,
code: 'ENOENT',
path: '/Users/davidmckeown/dev/adt-com/node_modules/grunt-contrib/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/tmp/phantomjs-1.7.0-macosx.zip' }
Another message just above that contains:
npm ERR! phantomjs#0.2.6 install: `node install.js`
npm ERR! `sh "-c" "node install.js"` failed with 8
npm ERR!
npm ERR! Failed at the phantomjs#0.2.6 install script.
npm ERR! This is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 12.2.1
npm ERR! command "node" "/usr/local/bin/npm" "install" "grunt-contrib"
npm ERR! cwd /Users/davidmckeown/dev/adt-com
npm ERR! node -v v0.10.0
npm ERR! npm -v 1.2.14
npm ERR! code ELIFECYCLE
Any help figuring out what is causing problems here would be fantastic. This happens with other modules too, from what I can tell.
npm cache clean
or if installed under su
sudo npm cache clean
There was an issue 5 months ago with grunt qunit package - https://github.com/gruntjs/grunt-lib-phantomjs/issues/5.
Try to install this specific package:
sudo npm install grunt-contrib-qunit
The package that you installed is a bundle of many packages. The qunit package version was not updated explicitly to the latest version in this bundle, that's why clearing the npm cache might solve this issue.