I have problem with installations errors when i use ..
npm install -g newman-reporter-htmlextra
I don't realy know how to solve this problem.
Its happend olny with htmlextra raports when i install htlm raports its work normaly.
C:\Users\MW\Newman_testy>npm install -g newman-reporter-htmlextra
'CALL "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g' is not recognized as an internal or external command,
operable program or batch file.
npm WARN deprecated highlight.js#9.18.5: Support has ended for 9.x series. Upgrade to #latest
npm WARN deprecated gulp-header#1.8.12: Removed event-stream from gulp-header
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
C:\Users\MW\AppData\Roaming\npm\newman-reporter-htmlextra -> C:\Users\MW\AppData\Roaming\npm\node_modules\newman-reporter-htmlextra\bin\htmlextra.js
highlight.js#9.18.5 postinstall C:\Users\MW\AppData\Roaming\npm\node_modules\newman-reporter-htmlextra\node_modules\highlight.js
node deprecated.js
npm WARN newman-reporter-htmlextra#1.21.0 requires a peer of newman#^5.1.2 but none is installed. You must install peer dependencies yourself.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn C:\Program Files\Java\jdk1.8.0_291
npm ERR! file C:\Program Files\Java\jdk1.8.0_291
npm ERR! path C:\Program Files\Java\jdk1.8.0_291
npm ERR! errno -4058
npm ERR! highlight.js#9.18.5 postinstall: node deprecated.js
npm ERR! spawn C:\Program Files\Java\jdk1.8.0_291 ENOENT
npm ERR!
npm ERR! Failed at the highlight.js#9.18.5 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\MW\AppData\Roaming\npm-cache_logs\2021-08-20T12_08_29_915Z-debug.log
Related
I am getting below error while I am trying to install npm modules using
npm install
I already have npm and node.js installed.
npm WARN config global --global, --local are deprecated. Use --location=global instead.
npm WARN using --force Recommended protections disabled.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path C:\Users\test/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\test\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\test\AppData\Local\npm-cache_logs\2022-10-20T11_34_43_246Z-debug-0.log
I am unable to install yo from npm I have found these errors while running installation of yo, I have made all the paths for environment variables, but still getting error, i have also cleared the cache and re-install the nodejs , reboot my pc but still getting this error
$ npm install --global yo
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
C:\Users\hp\AppData\Roaming\npm\yo -> C:\Users\hp\AppData\Roaming\npm\node_modules\yo\lib\cli.js
C:\Users\hp\AppData\Roaming\npm\yo-complete -> C:\Users\hp\AppData\Roaming\npm\node_modules\yo\lib\completion\index.js
spawn-sync#1.0.15 postinstall C:\Users\hp\AppData\Roaming\npm\node_modules\yo\node_modules\spawn-sync
node postinstall
npm#1.0.0 C:\Users\hp\AppData\Roaming\npm
`-- (empty)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn-sync#1.0.15 (node_modules\yo\node_modules\spawn-sync):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn-sync#1.0.15 postinstall: node postinstall
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status -4058
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--global" "yo"
npm ERR! node v6.9.2
npm ERR! npm v3.10.9
npm ERR! file ;C:\Program Files\Git\bin;C:\Program Files\Git\cmd
npm ERR! path ;C:\Program Files\Git\bin;C:\Program Files\Git\cmd
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn ;C:\Program Files\Git\bin;C:\Program Files\Git\cmd
npm ERR! spawn-sync#1.0.15 postinstall: node postinstall
npm ERR! spawn ;C:\Program Files\Git\bin;C:\Program Files\Git\cmd ENOENT
npm ERR!
npm ERR! Failed at the spawn-sync#1.0.15 postinstall script 'node postinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the spawn-sync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node postinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs spawn-sync
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls spawn-sync
npm ERR! There is likely additional logging output above.
npm#1.0.0 C:\Users\hp\AppData\Roaming\npm
`-- (empty)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn-sync#1.0.15 (node_modules\yo\node_modules\spawn-sync):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: spawn-sync#1.0.15 postinstall: node postinstall
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status -4058
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "--global" "yo"
npm ERR! node v6.9.2
npm ERR! npm v3.10.9
npm ERR! Callback called more than once.
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! C:\Users\hp\npm-debug.log
npm ERR! code 1
Please tell me what is the problem with it.
Just install the latest version of nodejs and the error will get resolved.
Type the instructions in the terminal and node js will get updated:
$ sudo apt purge nodejs (for removing previous files of node js)
$ wget -qO- https://deb.nodesource.com/setup_7.x | sudo bash -(it will download latest version of node)
$ sudo apt-get install nodejs
and it is done.
Happened to me too... in recent distributions many packages install nodejs as the node.js executable, while spawn-sync attempts to call node, that is why this fails.
As a workaround, you can create a softlink from node to nodejs. Something like:
sudo ln -s `which nodejs` /usr/bin/node
I'm going to install slamdata on debian Jessie, as described here, but I failed at npm install section and it wanted to install chromedriver. I even tried a mirror of chromedriver. Here is logs.
exec#mob-db1:/opt/slamdata$ npm install
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
chromedriver#2.23.1 install /opt/slamdata/node_modules/chromedriver
node install.js
Downloading http://chromedriver.storage.googleapis.com/2.23/chromedriver_linux64.zip
Saving to /tmp/chromedriver/chromedriver_linux64.zip
Receiving...
ChromeDriver installation failed undefined
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.14
npm ERR! Linux 4.2.8-1-pve
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.4.0
npm ERR! npm v3.10.6
npm ERR! code ELIFECYCLE
npm ERR! chromedriver#2.23.1 install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromedriver#2.23.1 install script node install.js.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the chromedriver 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 information on how to open an issue for this project with:
npm ERR! npm bugs chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /opt/slamdata/npm-debug.log
exec#mob-db1:/opt/slamdata$ npm install chromedriver --chromedriver_cdnurl=http://npm.taobao.org/mirrors/chromedriver
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into
npm and is now out of date with respect to npm
chromedriver#2.23.1 install /opt/slamdata/node_modules/chromedriver
node install.js
Downloading http://npm.taobao.org/mirrors/chromedriver/2.23/chromedriver_linux64.zip
Saving to /tmp/chromedriver/chromedriver_linux64.zip
Receiving...
ChromeDriver installation failed undefined
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.14
npm ERR! Linux 4.2.8-1-pve
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "chromedriver" "--chromedriver_cdnurl=http://npm.taobao.org/mirrors/chromedriver"
npm ERR! node v6.4.0
npm ERR! npm v3.10.6
npm ERR! code ELIFECYCLE
npm ERR! chromedriver#2.23.1 install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromedriver#2.23.1 install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the chromedriver 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 information on how to open an issue for this project with:
npm ERR! npm bugs chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /opt/slamdata/npm-debug.log
I met it with 'yarn install' which info 'chromedriver: ChromeDriver installation failed Error with http'.So i try to install chromedriver before 'yarn install'.
And then solve it.
https://www.npmjs.com/package/chromedriver
If you are not able to install chrome driver through npm, use the binary files of chrome driver. Make sure you download the same version binary file as that of your chrome browser.
Go to: https://chromedriver.chromium.org/
This will give you an exe file.
Put this file in user/AppData/Roaming/npm directory.
set this to PATH environment variables.
Thats it! You are done :)
This is error that I'm getting in cmd prompt:
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
> angular2-quickstart#1.0.0 postinstall C:\Users\hp\Desktop\angular2-seed
> typings install
'typings' is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.12
npm WARN angular2-quickstart#1.0.0 No description
npm WARN angular2-quickstart#1.0.0 No repository field.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe"
"C:\\Users\\hp\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v4.4.7
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! angular2-quickstart#1.0.0 postinstall: `typings install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular2-quickstart#1.0.0 postinstall script 'typings install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular2-quickstart package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! typings install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs angular2-quickstart
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls angular2-quickstart
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\hp\Desktop\angular2-seed\npm-debug.log
When you see
'typings' is not recognized as an internal or external command, operable program > or batch file.
try to install typings first npm install typings --global
You need to install typings globally:
- npm i typings -g
I want to run meteor application on windows after developting it some time on mac. when I run meteor command it states this error:
=> Started proxy.
=> Started MongoDB.
npm-container: updating npm dependencies -- lather_headers, azure-graphapi, xml2json, node-forge, websocket, googleapis, request, path, gmail-api-create-message-body, request-promise, node-ews-noloop,
http-proxy...
=> Errors prevented startup:
While building package npm-container:
error: couldn't install npm packages from npm-shrinkwrap: Command failed: gypnpm WARN enoent ENOENT, open 'C:\c\liso_service\packages\npm-container\.npm\package-new-1e8tkgh\package.json'
npm WARN package-new-1e8tkgh No description
npm WARN package-new-1e8tkgh No repository field.
npm WARN package-new-1e8tkgh No README data
npm WARN package-new-1e8tkgh No license field.
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Users\\Administrator\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.4_1\\mt-os.windows.x86_32\\dev_bundle\\bin\\\\node.exe"
"C:\\Users\\Administrator\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.4_1\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v0.10.45
npm ERR! npm v3.9.6
npm ERR! code ELIFECYCLE
npm ERR! node-expat#2.3.13 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-expat#2.3.13 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-expat 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 information on how to open an issue for this project with:
npm ERR! npm bugs node-expat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-expat
npm ERR! There is likely additional logging output above.
gypnpm WARN enoent ENOENT, open 'C:\c\liso_service\packages\npm-container\.npm\package-new-1e8tkgh\package.json'
npm WARN package-new-1e8tkgh No description
npm WARN package-new-1e8tkgh No repository field.
npm WARN package-new-1e8tkgh No README data
npm WARN package-new-1e8tkgh No license field.
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Users\\Administrator\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.4_1\\mt-os.windows.x86_32\\dev_bundle\\bin\\\\node.exe"
"C:\\Users\\Administrator\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.4_1\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v0.10.45
npm ERR! npm v3.9.6
npm ERR! code ELIFECYCLE
npm ERR! node-expat#2.3.13 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-expat#2.3.13 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-expat 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 information on how to open an issue for this project with:
npm ERR! npm bugs node-expat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-expat
npm ERR! There is likely additional logging output above.
=> Your application has errors. Waiting for file change.
I can see what is the error message. But I do not know haw do I get directory package-new-1e8tkgh instead of just package
I have correct versions of node and npm, that are mentioned in error:
npm ERR! node v0.10.45
npm ERR! npm v3.9.6
This was warking while I had meteor version 1.2.0.2 and I was using node version 0.10.40. But since meteor upgrade to 1.3.4.1 it stopped.
I also have visual studio 2012 and python 2.7 installed. ( as it says on some previous sources, that this was necessary to run and build meteor on windows. like this one )
OS is windows server 2012, I have tried on Win 7, 8 and 10 but it does not work. Event the old meteor version 1.2.0.2 was just working on Windows server 2012.
What should I do to get this working? Why is this happening at all. Should not I just install newer node version and go on. Like in this case from 0.10.40 to 0.10.45.
Please advise.