-
Notifications
You must be signed in to change notification settings - Fork 247
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
npm global installation fails on Windows #964
Comments
Hi @s-KaiNet, that's a strange one. The fact that the error is actually "Access is denied" makes me curious if there's some other process that's somehow affecting the ability to move the files. What's also strange is we have retry behavior baked in for that operation, so if it fails it should retry for up to 30 seconds. |
I'm having the same issue trying to upgrade
|
I'm getting same error with npx, did you manage to fix the problem ? |
@imadhy The only way I made it install properly was by running Volta from an administrator console, and even then, only for a few tools. |
in npm 7+, npx is built in, and the separate npx package shouldn’t be used. |
Looks like Volta doesn't work on non admin profiles in Windows. |
Same issue on my env, but it was fixed by enabling |
I made a test and it looks like the use of symlinks are unnecessary. I ran Am I missing something or Volta could run totally without the need of symlinks on Windows? If yes, it would be a huge security enhancement, as Developer Mode enable much more the symlinks and Microsoft discourages the use of symlinks. For example, in my company is very difficult for someone have admin rights or have Developer Mode enabled for security reasons. |
I use node@12 and built-in npm. I'm trying to install the Yeoman generator:
At the last step I see an error
Volta error: Could not create environment
, logs:And also below events from proc monitor:
When I run
npm install generator-code -g
to install another generator, it works well.I don't have antivirus and even Windows Defender is switched off since that's a developer VM.
It looks like the issue only appears with huge generators with lots of files (like
@microsoft/generator-sharepoint
)The text was updated successfully, but these errors were encountered: