Running:
npm install #truffle/hdwallet-provider
gives me ECONNRESET after being stuck on rollbackFailedOptional.
Already tried the first 2 solutions from here. Already tried running npm install again, this one is working properly.
More info on the packet: https://www.npmjs.com/package/#truffle/hdwallet-provider
Yes, I do have Web3 1.2.11, Node v14.3. I am running the command in a VSCode terminal, I have a stable internet connection.
What can I do to fix this?
A simple terminal reset was not enough.
A clean restart of the laptop fixed it (shut down + power on).
What happened is completely beyond me. Maybe this will help somebody else.
Related
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.
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.
Installing an NPM package (in this case 'zos') hangs at :
>npm install zos
fetchMetadata: sill resolveWithNewModule http-https#1.0.0 checking installable status
Seems kind of strange as this has only recently started occurring. Other packages seem not to have this issue...
I am using the following environment:
Arch Linux
Node v11.9.0
NPM v6.9.0
I can install other npm packages without issues (eg, lodash, truffle, web3)
OK, I managed to fix the issue... last week I was having some issues with internet access in a new location with wifi so I had to hack around a bit with my /etc/resolv.conf file to get general internet access again... turns out that while that fixed my general browsing it had a knock on effect on npm installs!
So in summary to fix the issue I replaced my /etc/resolve.conf file which had only the following line in it:
# Generated by NetworkManager
nameserver 192.168.0.1
with a previous version of the file I had saved which had the following contents:
nameserver 127.0.0.53
options edns0
And Walah! Everything works again, including the 'npm install zos'....
Thanks to anyone who was looking into this for me!
Cheers
Rick
So I'm just setting up my Discord bot in a new machine. I used the latest Node version in LTS and I have Windows Build Tools installed.
But doing npm install, everything is going well until the part when the sqlite3 package is being installed. I have a log here for reference: https://pastebin.com/ktJ8VyZY
And another log straight from PowerShell: https://pastebin.com/d232rjJY
Before I had issues with Python and that has been resolved but right now I cannot pinpoint exactly what is the problem and I've been reading all lines related to gyp and the problem isn't really clear for me so I'm here if anyone can pinpoint the exact problem and the ways to solve it.
Thank you.
Package.json if needed: https://pastebin.com/ACh0mQRe
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!