You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm is producing incorrect or undesirable behavior.
Other (see below for feature requests):
What's going wrong?
I run npm install on windows 10 within cmd.exe.
After installation is complete the prompt updates properly, but some spawned child-process do not exit and run forever and show up in my TaskManager.
How can the CLI team reproduce the problem?
Open TaskManager
run npm install of any npm project
monitor the task manager - you will observe that some node scripts never die 😕
supporting information:
npm -v prints: 5
node -v prints: tried with node 6 and latest 10 - same result
npm config get registry prints:
Windows, OS X/macOS, or Linux?: Windows
Network issues:
Geographic location where npm was run:
I use a proxy to connect to the npm registry.
I use a proxy to connect to the web.
I use a proxy when downloading Git repos.
I access the npm registry via a VPN
I don't use a proxy, but have limited or unreliable internet access.
Container:
I develop using Vagrant on Windows.
I develop using Vagrant on OS X or Linux.
I develop / deploy using Docker.
I deploy to a PaaS (Triton, Heroku).
The text was updated successfully, but these errors were encountered:
I'm opening this issue because:
What's going wrong?
I run
npm install
on windows 10 withincmd.exe
.After installation is complete the prompt updates properly, but some spawned child-process do not exit and run forever and show up in my TaskManager.
How can the CLI team reproduce the problem?
npm install
of any npm projectsupporting information:
npm -v
prints:5
node -v
prints: tried with node6
and latest10
- same resultnpm config get registry
prints:The text was updated successfully, but these errors were encountered: