npm view in stubbed-out npm-world hangs
See original GitHub issueNot sure if this is a problem with my setup or if it’s a problem with how-to-npm, but when I do npm view my-package-name
as instructed by the verification message in challenge 07 (Publish), it just hangs. Outside the directory I created for the how-to-npm workshopper, npm view whatever
works just fine, returning data about packages that exist or an 404 error for packages that don’t exist.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:2
- Comments:9 (3 by maintainers)
Top Results From Across the Web
npm install hangs - node.js - Stack Overflow
To see if your container (or even your host) can resolve hosts, you can try running: curl https://github.com . In my case I...
Read more >[BUG] npm install will randomly hang forever and cannot be ...
I've tried using Process Explorer to check for handles to files in the project directory from other processes but there are none. There...
Read more >Common errors | npm Docs
npm hangs on Windows at addRemoteTarball Look for lines defining the tmp config variable. If you find more than one, remove all but...
Read more >npm-view
This command shows data about a package and prints it to stdout. As an example, to view information about the connect package from...
Read more >wait-on - npm
wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here’s a solution that worked for me:
That worked for me.
The problem is that for some reason, the local registry stops working, so to trigger it to start working again, one has to go back to the Login step.