npm install stack error win32-x64-57_binding.node not found - npm-install

When I run with npm install,I got this error.This is the error message
I already reinstalled node and delete all npm or npm cache in C Disk,but the error still happen

Node 9 (module 57) isn't supported for node-sass 4.5.0. You need to upgrade to 4.7.2 or downgrade your Node version

Related

error installing cypress on windows 64 with npm

I'm seeing an error when attempting to install the latest cypress on my Windows 10 machine. I was using cypress 8.7 just fine. I deleted node_modules and package-lock.json and removed "cypress": "^8.7.0", from package.json.
Now installing cypress (9.1) I see this error:
npm install --save-dev cypress
npm ERR! Error: Cannot find module 'har-validator'
I see the same error when trying to use the old version too
npm install --save-dev cypress#8.7.0
System info from powershell:
node -v
> v16.8.0
npm -v
> 7.21.0
UPDATE:
My friend is able to install with dependency 8.7.0 in package.json, on OSX with nodejs 14.16.0.
This works today (2021-11-26) for me
npm install --save-dev cypress#8.7.0
There is a Bug in #cypress/request.
Take a look at https://github.com/cypress-io/request/pull/15
EDIT: There is a PR from one of the devs. https://github.com/cypress-io/request/pull/16
Looks like Cypress issue with latest versions. we have this problem for v8.7.0 today. "npm install har-validator" manually installed the missing har-validator module, that helped.

Unable to install 'node-red-contrib-tf-model' using NPM on windows10x64

I followed the tutorials below for the installation of the tensorflow model:
https://flows.nodered.org/node/node-red-contrib-tf-model
https://github.com/tensorflow/tfjs/blob/master/tfjs-node/WINDOWS_TROUBLESHOOTING.md
Steps taken:
I first installed the #tensorflow/tfjs-node inside Node-RED directly by running the following code:
C:\Users\username\.node-red\node_modules> npm install #tensorflow/tfjs-node#1.4.0
Ran npm install under C:\Users\username\.node-red\node_modules\#tensorflow\tfjs-node:
C:\Users\username\.node-red\node_modules\#tensorflow\tfjs-node> npm install
Finally ran npm install node-red-contrib-tf-model in the same directory:
C:\Users\username\.node-red\node_modules\#tensorflow\tfjs-node> npm install node-red-contrib-tf-model
Error that occured:
npm WARN node-red-contrib-tf-model#0.1.11 requires a peer of #tensorflow/tfjs-node#^1.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN #tensorflow/tfjs-node#1.4.0 No license field.
I have installed the correct tfjs-node version, and so why does this error occur?
Edit: Tried installing the module straight from Node-RED itself and got the following
ERROR:The specified module could not be found.
C:\Users\username\.node-red\node_modules\#tensorflow\tfjs-node\lib\napi-v6\tfjs_binding.node
When I checked the above directory it turns out that I do have the 'tfjs_binding.node'.
What am I doing wrong here? Can someone please help me out.

'npm ERR! 404 Not Found: async-validator' while installing Element-UI

I keep getting
npm ERR! 404 Not Found: async-validator#~1.8.1
while trying to install Element-UI. Tried installing async-validator through npm and got the same error, tried reinstalling Node, ...
node v10.2.1
npm 6.1.0
Any help is appreciated
EDIT:
I followed the first link MantasPtr commented and was able to install async validator like so:
npm install https://github.com/yiminghe/async-validator/archive/1.8.2.tar.gz
Do not specify the version code while installing a new version of library using npm. It might download the order version of that library
Specify the library name as it is to install the latest version or specify #latest
npm install async-validator --save
or
npm install async-validator#latest --save
May be, this is a temporary solution:
npm install https://github.com/yiminghe/async-validator/archive/1.8.1.tar.gz
if you try to load npm install https://github.com/yiminghe/async-validator/archive/1.8.2.tar.gz in a browser, you will see {"error":"Not found"} as a result.
but https://github.com/yiminghe/async-validator/archive/1.8.1.tar.gz will be found. So I work with an older version and will look for an update later.

npm install error - cb() never called

I try to install node_module in my angular project what I downloaded, but I get this error:
npm ERR! registry error parsing json
Then i reinstall npm using npm intall npm -g and after when i try use npm install I get this error:
(node:11252) UnhandledPromiseRejectionWarning: Unhandled promise
rejection (rejection id: 1): Error: ENOENT: no such file or directory, stat
'C:\Users\User\AppData\Roaming\npm-cache\_cacache\tmp\git-clone-ec5da46c\angular\cdk.es5.js'
debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\User\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install' ]
2 info using npm#5.4.2
3 info using node#v6.10.2
4 verbose npm-session ff5ce249dfe37f0e
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall spa#0.0.0
7 info lifecycle spa#0.0.0~preinstall: spa#0.0.0
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 silly install loadShrinkwrap
13 info lifecycle #angular/cdk#2.0.0-beta.10-a7ce31e~prepack: #angular/cdk#2.0.0-beta.10-a7ce31e
14 error cb() never called!
15 error This is an error with npm itself. Please report this error at:
16 error <https://github.com/npm/npm/issues>
I already tried npm cache clean --force but i get same error.
node -v v6.10.2
npm -v 5.4.2
I had the same issue. I resolved it
by excluding package-lock.json file
npm i --no-package-lock
OR by manually deleting package-lock.json
Run npm cache clean --force and perform an install.
I had the same issue. I resolved it by remove nodejs#10 and install nodejs#8
On Windows 10 running npm install gave me this error.
I solved this issue by doing so from within Administrator: Command Prompt.
Ensure that you have a package.json file within the root of your angular project which should look something similar to this.
https://github.com/heroku/node-js-sample/blob/master/package.json
If the package.json file exists, you run npm install to get the packages saved to it and that will generate a node_modules directory for you.
However, if the file does not exist, it means you have to initialize npm into the project by running npm i -y which should automatically create a package.json file for you and as well allow you to install node modules.
NB: You have npm installed on your machine already so running npm install npm -g is not ideal.
I got this error when my package.json referred to a package using file:../(local path) and the directory didn't exist. Pointing it to the correct path resolved the error.
In my case... none of the above worked. I then deleted my package-lock.json. When I ran an npm install I got an error that a certain package could not be found in the repository. When I removed that from package.json my npm install worked!
I had the same issue. In my case it was caused by a syntax error within the .npmrc file, which was manually edited
Method 1:
npm cache clean --force then install your package
Method 2:
Disable your antivirus software and try to install your package
Method 3:
It is your internet connection, if you are using Wifi or an Ethernet connection use your cellular network or a different network and try to install your package

npm generator-ionic Install Requires yo#>=1.0.0

I'm trying to install generator-ionic, and I get the following fatal error:
EPEERINVALID generator-ionic#0.7.3 requires a peer of yo#>=1.0.0 but none was installed
I'm using node 0.12.17, npm 3.3.6, and yo 1.4.7, so I do not understand what isn't satisfied.
#chrysanhy I think I found the issue. I just downgraded my npm version to 2.7.4 and when I ran the command npm install generator-ionic-g the following message appeared:
npm WARN peerDependencies The peer dependency yo#>=1.0.0 included from generator-ionic will no longer be automatically installed to fulfill the peerDependency in npm 3+. Your application will need to depend on it explicitly.
Now the ionic-generator is working fine on my machine. Hope this helps you and everyone who is facing the same problem.