Skip to content
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

[Issue]: npm i taking to long when running through nvm-windows #1125

Open
contibru opened this issue Apr 16, 2024 · 1 comment
Open

[Issue]: npm i taking to long when running through nvm-windows #1125

contibru opened this issue Apr 16, 2024 · 1 comment

Comments

@contibru
Copy link

What happened?

When I am executing a npm i command with the nvm-windows turned on, the time to get all packages is takeing to much time.
I already disabled all ipv6 resources and the issue is still happening.
When I turn off the nvm by using nvm off command and then trying to execute npm i again using the node installation directly, everything works fine and fast.
Also, even with the IPv6 disabled, nvm debug is showing enabled.

IPV6 disabled:
image

What did you expect to happen?

The time Downloading packages should be the same with or without nvm-windows or at least pretty equals.

Version

1.1.11 or newer (Default)

Which version of Windows?

Windows 11+

Which locale?

English (Default)

Which shell are you running NVM4W in?

PowerShell

User Permissions?

Administrative Privileges, Elevated

Is Developer Mode enabled?

No (Default)

Relevant log/console output

No response

Debug Output

Running NVM for Windows with administrator privileges.

Administrator: PowerShell
Windows Version: 10.0 (Build 22631)

NVM4W Version:      1.1.12
NVM4W Path:         C:\Users\conti\AppData\Roaming\nvm\nvm.exe
NVM4W Settings:     C:\Users\conti\AppData\Roaming\nvm\settings.txt
NVM_HOME:           C:\Users\conti\AppData\Roaming\nvm
NVM_SYMLINK:        E:\nvm\node
Node Installations: C:\Users\conti\AppData\Roaming\nvm

Total Node.js Versions: 3
Active Node.js Version: v21.7.1

IPv6 is enabled. This can slow downloads significantly.

No problems detected.

Anything else?

No response

@coreybutler
Copy link
Owner

npm doesn't run through NVM for Windows. NVM4W creates a symlink to executables, so they are all run directly.

NVM4W checks to see if the ::1 address is available, which is how the OS indicates IPv6 is active.

From the description, it sounds like IPv6 isn't really turned off. It's entirely possible NVM4W may need a more explicit check, but if you're getting slow downloads on an app that doesn't touch NVM, something else is likely slowing it down... and IPv6 seems like a strong candidate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants