NPM install stuck - node.js

I'm trying to npm install mssql but it keeps getting stuck. How do I fix this issue. I've tried npm cache clean --force and npm i but nothing works. This is a new project so there isn't any node modules either

Related

npm i not working? npm ERR! Unexpected token '.'

My npm install seems to have stopped working out of nowhere, regardless of if i do npm i or npm install I keep getting an error saying npm ERR! Unexpected token '.' The other npm commands seem to be working perfectly but I can't install any modules because of this error. I'm using npm 8.7.0 and node v14.18.1
The simplest solution I could find and what worked for me was completely removing and unisntalling everything to do with nodejs and npm from my laptop. I then reinstalled it back with no issues and am able to use the command now.
As mentioned in one of the answers, try deleting the node_modules folder and package.lock.json. Use
sudo npm install
And if that doesn't work, what I would suggest is that you use yarn. If you don't know what yarn is, it's just a package manager like node.
You can install yarn by using the following command:
npm install -g yarn
After this make sure all the node modules and package.lock.json is deleted. Now run the command
yarn install
Hopefully, this will fix your issue.

how do I resolve this node-sass installation error

npm ERR! Unexpected end of JSON input while parsing near '...--END PGP SIGNATURE--'
I keep getting this error while trying to install node-saas. I have even tried disabling anti-virus & windows defender.
I am using this command to install node sass:
npm install node-sass
Please check the below steps:
Please delete your package.lock.json file, along with that delete your node_modules folder.
Then clear all your npm cache by npm cache clean --force.
Install node-sass globally by using npm install -g node-sass
Once done with node-sass that run your npm install && npm start.
Hope this should work fine.

Unable to install create react app on windows 10

I am new to react and when I run npx create-react-app my-app I get the following error message
I am using 14.5.0 for node and 6.14.8 for npm.
What I have tried so far to resolve the issue:
Uninstall and reinstall node
npm i --no-package-lock
npm cache clean --force
npm cache verify
I've tried running it with npm instead of ntx after installing create-react-app but this also fails

Unable to add firebase to react app with "npm install firebase"

I am trying to add firebase to my react app.But when I type npm install firebase I get strange error like:
Unexpected end of JSON input while parsing near 'Error message '. Error message is different every time i run npm install firebase.I have looked this questions:
Firebase npm install error
Unable to do "npm install --save firebase"
Firebase - Failing to install firebase using npm but yarn works
I have tried npm cache clean --force,and after npm update ,but that didn't work.Also I have tried downgrading npm,but that either did not work.Also I have tried uninstalling node,and installing again ,but that did not help either.Thanks in advance
npm version 6.13.7
node version v12.19.0
How about just to be sure remove package-lock.json and delete node_modules folder with rm -rf node_modules?
And after that npm install again.
Good luck.
It looks like npm cache was corrupted ,but as npm cache clean --force did not work,deleting _cacache directory in C:\Users\User\AppData\Roaming\npm-cache solved my problem.After that npm install worked just fine.

Why does the newest Angular CLI have a corrupted packages?

I installed the latest Node and Angular on Windows 10
npm install npm#latest -g
npm install -g #angular/cli#latest
But when I try to start a project ng new new-project I get the following error
npm WARN tarball tarball data for #angular/compiler#^6.1.0 (sha512-TY6axB1c7VvYXf+ebFDq3Ej+edgii3CDxew8HnyTFAWeDF2Gh8io1vTYwtdyDka6U53ASaheM1HpiUjzvYH0jQ==) seems to be corrupted. Trying one more time.
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\admin\Desktop\...\node_modules\.staging\#angular\common-6be83a81\locales\si.js'
...
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\admin\AppData\Roaming\npm-cache\_logs\2018-10-08T01_01_48_404Z-debug.log
Package install failed, see above.
I tried to uninstall Node.js and Angular CLI completely and then reinstall again
npm install npm#latest -g
npm install -g #angular/cli#latest
But still the same error ..... So I googled this issue. It seems like some people had it too, but then it magically disappeared for some people.
How to fix this?
I was getting the same below error when attempting to a create new project using ng new command.
npm WARN tarball tarball data for #angular/compiler#~7.2.0
(sha512-5yb4NcLk8GuXkYf7Dcor4XkGueYp4dgihzDmMjYDUrV0NPhubKlr+SwGtLOtzgRBWJ1I2bO0S3zwa0q0OgIPOw==)
seems to be corrupted. Trying one more time.
I tried many things but what did not worked and what finally worked for me I have listed below. My working node version is 12.2.0 and npm version is 6.9.0 (i.e. latest version).
What did not worked:
Downgraded node js to other lower versions (tried many version)
Deleted package-lock.json file from project and executed npm install
Executed npm install --registry https://registry.cnpmjs.org instead of npm install
Deleted npm and npm-cache folders from AppData\Roaming and then again installed node js
Deleted node_modules folder, executed npm update and then executed npm install
Executed npm cache clean --force and then executed npm install
Reinstalled #angular/cli
Checked for any firewall / antivirus (in my case it was disabled)
Opened node command prompt as an administrator
Checked user permissions for the project folder
Finally what worked is:
Installed the component for which it was giving error. npm install -global #angular/compiler
I had the same problem with node 12.13.0 and npm 6.13.0
npm WARN tarball tarball data for #angular/compiler#^7.2.11 (sha512-5yb4NcLk8GuXkYf7Dcor4XkGueYp4dgihzDmMjYDUrV0NPhubKlr+SwGtLOtzgRBWJ1I2bO0S3zwa0q0OgIPOw==) seems to be corrupted. Trying one more time.
For me the problem was npm. After upgrading npm to the newest version with npm i -g npm#latest the problem vanished. So it seems to be a problem with npm itself and not the Angular/CLI.
upgrade your NPM version use this command i -g npm#latest it works like magic

Resources