How to stop angular-cli freezing on "loadRequestedDeps: silly install loadAllDepsIntoIdealTree"? - npm

I am running Windows 8.1 with node version 7.7.3 and npm version 4.1.2.
I have been working on an Angular tutorial without issues. At some point since finishing that tutorial I installed Python. I am not sure if it is related, but I have mentioned it just in case.
Today I am trying to create an Angular application and it hung without completing.
I did some research and it tells me to do this:
npm uninstall -g #angluar/cli
npm cache clean
npm install -g #angular/cli
The last command hangs at this point:
loadRequestedDeps: silly install loadAllDepsIntoIdealTree
I opened the command prompt "run as administrator" to run these commands.
Everything I try fails. I have connected to a completely different network to eliminate that as the problem and that didn't fix anything. I have uninstalled and reinstalled node.js and that hasn't fixed the problem either.
I can ping registry.npmjs.org just fine.
What is causing this error?

I finally found the answer! I ran the following command in the command window:
echo %temp%
It had 3 temp paths in there. I removed the two I didn't need and voila, it works!

Related

Installing freeCodecamp locally hangs when I get to the npm ci step

I've been trying to install freeCodeCamp repo locally coz I'm doing the Full-stack curriculum and I am in a remote area where the grid is not reliable.
I've got the repo on my compute already. I've also installed MongoDB and Nodejs and Npm, following instructions and steps posted on Github by the freeCodeCamp Team. When I get to the step where dependencies need to be installed using "npm ci", the progress bar runs untill halfway, then it stops forever (sometimes it freezes the whole system).
I've tried with Git Bash, Powershell, and Powershell ISE with same results. I did uninstall and re-install Nodejs and NPM a couple of times for no avail. The versions are Node v16.17.0 and Npm 8.18.0.
Any HELP will be appreciated.
I'm having similar issues with v16.17.0 and npm v8.18.0. Downgrading to v8.13.0 seemed to fix it for me but I can't find any previously raised issues as to why this may be the case.
To downgrade:
npm i -g npm#8.13.0 && npm install
Seems to occur from v8.14.0 onwards

NPM stuck on idealTree: timing idealTree

Today i decided to start react native cli project. Everything works great since i want to add new lib of course using npm . So i ran npm install ... . And this command always stuck on
Image
idealTree: timing idealTree Completed in 3440ms
And nothing happened. So i tried to ran
npm install --verbose
And again stuck on the same place. Also clear cache npm cache clear --force and nothing happened again. I don'n know how to fix this
I have had npm install freeze on me numerous times, lately. I'm not sure of the cause. When that happens I follow these steps:
Kill the npm install process with ctrl+c.
Delete node_modules. If there are files that you cannot delete because they are currently in use, that may mean that the npm install process was not successfully stopped. Try opening Task Manager and ending all nodejs and terminal processes. If this fails, restart your pc and then delete node_modules
Clean cache and reinstall node_modules with npm cache clean --force && npm i
This has happened to me a few times before and all I had to do was kill my dev server before running npm install.
Hope that helps as well!
I had the same issue on node latest version v18.8.0 and npm v8.18.0, I just downgraded to node 16.6 using nvm and it worked fine.
For me, the issue was that I had node running for a separate project. Terminating the other node process fixed the issue.
When i opened my package.json i saw '~2.2.1' in front of react-native-gesture-handler which probably means that it was notinstalled properly
Just close all terminals and then open task manager and kill all the processes corresponding to NodeJS. Then install it again.
Hopefully it will resolve.
I also faced this problem and the solution was simple by stopping all the "nodejs terminals" that are working outside.
When you stop nodeJS Terminals running in the background, it will complete the current installation process.
enter image description here
When you want to add package on your project it is better to stop server before adding new package.
I had same problem but after doing this it is solved.

-bash: ... command not found npm

I’m getting that message after installing express globally.
I went through most of the solutions related to the /.bash_profile file and about exporting the correct PATH, but it still nothing works.
I tried this solution https://superuser.com/a/1081802 and it worked on the terminal, but when I close it and tried to execute the command express followed by the file I wanted to use, it ended up showing the same message.
Please help!
So I was looking for other kinds of solutions, and I remembered that I installed via the website and not by home-brew. Just in case, I uninstalled it and installed node again.
I run this:
npm install express -g
npm install express-generator -g
And up to this point it is now working.

Npm install makes Windows crash

Generally when I run npm install sometimes my pc crashes and shows the screen like the image below. I’ve tried removing both the package-lock.json and node_modules. I’ve also run the commands npm rebuild -g and npm cache clean -f.
2 days ago I reinstalled my pc to fabric settings and it still doesn’t help.
I’m using WSL, nodejs v12.10.0 and npm 6.10.3.
Anyone knows what’s up and could help me?
https://imgur.com/a/762AdrR
Update
I've been using yarn instead of npm since 3 months back and this problem has never occured again. So if you are experiencing the same problem as me, try it out.

"Node Commands" printed at prompt when trying to run grunt/ gulp on Windows 7

I've installed nodejs, and have used npm to install grunt using
npm install grunt
When I try to run grunt, I am presented with what appears to be instructions on running node commands: (see image)
the same applies when trying to run gulp
I have done the same steps on other computers, and had no problem running grunt previously
Please suggest ideas as to what's going on.
Thanks
As suggested by Joe Clay, the problem was that there was another app called node.exe whose pathwas in PATH variable before nodejs.
see also:
Nodejs seems to be not working; npm do work, however