-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] When using Docker image, installing package globally is hanging #7686
Comments
@cmerat The installation is not completing or it's taking time ? |
@milaninfy it eventually completes, usually taking between 5 and 10 minutes. A few months ago, it would complete in seconds. Not sure what is going on and the logs aren't verbose enough (even with silly level logging) to give me enough information. Would really love the log to have timestamps, too. Would really help with figuring out where it's hanging. I could be completely wrong, but from verbose logging I see in the shell, it's somewhere between lines 210 and 256 since the delay is between those two verbose lines being output to console. Lines here are file number lines, not the logging index at the start of each line. |
There is a problem with npm install since node 20 #nodejs/docker-node#1946 |
Could you please try with latest npm 10.9.1 ? |
Confirmed that it appears to be have been fixed with npm 10.9.1. Now takes a few seconds rather than minutes. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When installing a package globally, the installation "hangs" after "fetch/packumentCache" steps for minutes before proceeding and completing with a bunch of "placeDep" steps. This behavior started happening approximately two months ago and has continued since. This is making building the container images for my app very slow (5+ mins).
npm-install.log
Expected Behavior
The installation should not hang or, at the very least, give me feedback on what is taking so long.
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: