I am in a problem that when I try to install the mongoose node module than it starts to download but hangs out every time the operation can be stopped by ctrl C but the module cant be installed even after several trials
and every time it hangs out but if i try to install any other node module then there is no problem I am having the node version
19 and 18 LTS both i have tried and npm version 9 and 8
npm i mongoose
npm install mongoose
Related
Every time I run npm run build:ssr in angular CLI it gives me this error:
Node.js version v13.14.0 detected.
I have checked everywhere in my ubuntu but nodejs version 13.14.0 is not there.
Edit: When I run node -v it returns v16.15.0.
so i'm trying to install brain.js in my project so i can use it
to create a kind of chat app, trying to install it however gives me an error
i'v read in places you need 64 bit version of node and i'm fairly sure i have
that, i reinstalled it using nvm ( node version manager )
node -v returns v16.13.1
npm install brain.js
heres the error log it outputs:
https://pastebin.com/raw/xukfQJLY
While hosting my webapp on heroku I got a message of some bugs in my npm package, my npm package was of version 3 and node.js was of version 8, I wrote thinking that I can update my npm version I tried to update it but the version remained same so I decided to uninstall it and wrote the command "npm uninstall " and than again tried to install npm but in vain ,finally I uninstalled my node.js and reinstalled tha npm will automatically get installed with it, but this too didn't work now I have node of version 10 with no npm which I got to know by checking version of npm which gave me message of "command not found ", now my every try to install npm has failed , may anyone suggest me what I can do to restore my losses and resume my work.
I am not sure if you have Linux or Windows. First I would check if the npm folder is in path.
You can follow one of these two to add to path if it is not done yet.
Windows
Linux
Alternatively you can install node with node version manager (nvm):
nvm linux and mac
nvm windows
So I have a raspberry pi Model 3 B+ and I need NodeJS on it. It has actually been installed for a while now (2-3 weeks) and I have been building a server on it since then. NPM has worked and installed packages up until yesterday.
Yesterday, I had installed the package restify-clients, and I came back to see that NPM/Node had an incremental update (I think from 6.10.1 to 6.10.2 or something like that). So I copied the command it gave me and ran it, which I assumed would update the package. I'm choosing to believe these actions are the reason why NPM does not work anymore.
Running any npm command does not hang, it just returns like nothing was run.
Running which npm returns /usr/local/bin/npm, running sudo which npm returns the same. Running npm -v returns nothing, running /usr/local/bin/npm -v returns nothing. /usr/bin/npm points to /usr/lib/node_modules/npm/bin/npm-cli.js, /usr/local/bin/npm points to /usr/local/lib/node_modules/npm/bin/npm-cli.js.
Running any command like npm init or npm install does nothing as well.
I have tried reinstalling NodeJS from nodesources twice, and both times NPM is installed into the directories but running any NPM just returns.
For extra information, running nodejs -v and node -v works and returns a version number.
Any suggestions?
Thank you.
Uninstall node package and only keep nodejs, so npm should be working again.
I am using Mac OS Yosemite. I use npm install -g n to install the n module to try to upgrade nodejs. Then
I run
n stable
But I received an error during the upgrade and it quit unexpectedly.
Then when I type "node -v" I get an error:
Segmentation fault: 11
In fact I get this error when I type npm install and node so literally I can't use node or npm anymore.
What does it mean? how can I get my node.js back? I tried to reinstall it using
brew install node but after the install I still get the error.
Remove your node modules folder and try to reinstall. Depending on what version of node you were previously running your modules could need to rebuild for compatibility