NPM hanging on installing package 'zos' - npm

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

Related

E500 Internal Server Error When Installing Package in Atom

I'm currently trying to install the package atom-beautify to my Atom IDE. When attempting to do so I get the following error:
npm ERR! code E500
npm ERR! 500 Internal Server Error - GET https://www.atom.io/api/packages/atom-beautify/versions/0.33.4/tarball
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User.atom.apm_logs\2022-04-19T03_03_14_465Z-debug.log
I understand that this may be solved with downloading additional command-line tools as I currently only have the Windows default tools and Git.
If anybody could give me any information on how to fix this issue that would be great.
Thanks :)
I believe this is an issue with the Atom servers. Issue opened on Atom github portal.
https://github.com/atom/atom/issues/25417
Issue is from yesterday I think, I try to reinstall Atom several times and change the configuration but the issue persist, I search more information into Atom official blogs and didn't find like the root cause or anything related
Maybe server are down because is not related with the atom basic configuration or apm
Hope to solve soon.
The issue is with Atom servers. any package i tried to install these days fails.
An alternative to install atom-beautify is using its github repo.
So use
apm install Glavin001/atom-beautify
references to my answer
https://github.com/atom/apm/issues/355#issuecomment-116411783
https://github.com/atom/atom/issues/25417#issuecomment-1103834423
Use this to install any atom package available on github

npm not working - “read ECONNRESET” when installing hdwallet-provider

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.

-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.

Issues with installing sqlite3 in NPM

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

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

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!