For some reason my npm stopped working with network suddenly.
I didn't really get why, so I decided to look through the stackoverflow questions but all the answers I could find were about running npm behind corporate proxies, but I work at home and I don't have a proxy.
Below is a couple of screenshots of my console with npm errors:
Maybe someone has already encountered that problem and knows how to solve it?
PS: I've read one guy saying that I just need to wait a bit and that npm servers might just be down, but it's already been for 2 days and I can't use npm:(
I hope someone might help)
Thanks to Bidhan, the command npm config delete proxy solved the issue.
Related
I have encountered a problem with npm which gives me this weird error.
It seems the error is not related to a specific file, but it is something that occurs for some reason. Unfortunately I can't share any code, but after a research I found it has something to do with cache (maybe?). The process is happening on a kubernetes pod with different environments for multiple npm/nodejs installations running in parallel.
Has anybody encountered this problem or has more details and information on the matter?
Will update the post accordingly, thank you.
I am trying to install new angular 4. I have upgraded my node to the latest version, 6.11.2, and my npm to 3.10.10. I trying to install angular-cli globally but it took hours,still no success.
I see many of us have the same problem. I tried their solution by disabling my firewall as well as progress bar, unfortunately, no success in my case.
Can anyone help me please?
Thanks.
I found a solution from one of the posts on the forum. The problem was with the system environment variables, I had duplicate temp variables which were causing a crash during the execution. I have removed the duplicate variables and restarted my computer, and it worked perfectly. Hope it will help someone.
Our TFS build server does not have access to the internet. After getting node.js installed next I tried to install tfx-cli. using the command:
npm install -g tfx-cli
As far as I can tell, now it wants to download dependencies required. It looks like a whole web of dependencies - nuget style. Am I expected to set up an internal npm server with the dozens of dependencies required, becoming an expert on node.js and npm - just so I can add some custom commands to our TFS server?
Is there a version of tfs-cli I can get that includes all dependencies ?
I know this is old, but I just happened to come across your question. Hopefully this will help others.
Although I haven't tried it myself, there do seem to be ways of installing NPM packages offline. Here's one Stack Overflow answer that may get you pointed in the right direction. Another solution I've seen recommended is npmbox.
I've looked through the different articles here, but I'm not finding out the answer I need, or don't understand necessarily what has been explained in other posts.
I downloaded node.js got my github up and have cloned the phonecat site, that part works fine. I can even check npm/node versions through cmd, but whenever I install using either "npm install" or "npm install -g" "Couldn't read depndencies" couldn't find package.json" has a long list of errors:
http://tinypic.com/1r54rjf4
I have tried caching, updating, restarting, uninstalling, reinstalling, giving permissions to fully allow windows system32 for commands. I have been reading for a few hours, and I am just at a complete loss here. Any help would be greatly appreciated!
When you don't specify a module to download, npm will look for a package.json. It's not finding one, which is why you're seeing all kinds of errors.
Is there a project you're working on? If you want to start a new one you can run npm init. If there's an existing one that has a package.json, you can navigate to that directory in your terminal and then npm install should work.
I didn't. I'm still wrestling with it. I'm not sure what to do about it either. I had one of my friends come over that's familiar with node and he couldn't figure it out. It must be a permissions issue somewhere on the computer. I can't figure out what else it could be.
Well some days ago I was tired to always call sudo when calling npm install and that sort of things so I tried uninstalling node and tried installing via Homebrew, I managed to make a huge disaster but finally it worked. Until now...
When I run node app.js or npm install it just doesn't do anything.
I tried deleting the related files like this.
I tried using nvm.
Tried the manual install with the .pkg file from the node homepage.
Tried through homebrew again.
And still no luck; however if the Node app has compilation errors I get the error stack, but when everything is "ok", instead of start listening for incoming connections it just exits with code 0.
Ok, I feel reaaaaaaaaally stupid after I found the issue, in my postgresql config I had the wrong password for the database and for some reason caused all this mess. Will upvote all of you, will understand if you downvote me for being such a moron.
OneOfOne's node debug then keep pressing s did the trick for me.