Repository navigation
Infinite loop when running npm i #630
Description
Activity
Yikes! 😱 Thank you for reporting this (and for testing the beta for us)! A couple follow-up questions—
- does this ever show up with
yarnor only withnpm? - does it show up more in specific repos?
- does it happen in non-Powershell environments on Windows, e.g. in CMD?
- does this ever show up with
@dustinsoftware That's not good behavior 😦 I know I ran into issues with this in the past, and I documented some of what I found in this issue: #577 However, since we're using the
cmd.exe /C"workaround", it's a bit surprising to see it crop up again!Out of curiosity, is this in a project that has
nodepinned, or is it using the default Node / npm version (e.g. outside of a project or in a non-pinned project)? If it's outside of a pinned project, do you havenpmavailable from a separate installation, or is Volta the only Node / npm installation you have?Thanks for reporting and helping us test!
After installing
v0.7.0-beta3, I've now observed a few cases where runningnpm icauses thousands of processes to spawn. It's hard to tell if this is new behavior; I will attempt a downgrade if I can find a repro. Whenever this happens I have to log out of my workstation to get all the processes to close.(unreliable) Steps to repro:
npm i, observe it worksnpm iagain, observe it hangs and thousands of processes spawn