-
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] npm breaks on Windows when running off a UNC path #3349
Comments
hi @Stanzilla thanks for bringing it to our attention. Can you please open a new issue providing more info about the current environment, how exactly do you setup that Ubuntu WSL, how did you installed Node.js and npm. Also when you run an npm command can you use a more verbose logllevel. e.g: I'm going to close this issue since it's been stalled for a long time and haven't got any more traction but like I said, feel free to create a new one with more info in case you're able to still reproduce it using the current version of the npm cli ( |
@ruyadorno Hey there! I just updated npm to 8.5.2 and ran
Afterwards I nuked
Everything else is pretty much the same, so not sure if a new issue would help. |
Is there an existing issue for this?
Current Behavior
PS Microsoft.PowerShell.Core\FileSystem::\wsl$\Ubuntu\home\stan\projects\personal\WeakAurasCompanion> npm install
'\wsl$\Ubuntu\home\stan\projects\personal\WeakAurasCompanion'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
npm WARN saveError ENOENT: no such file or directory, open 'C:\Windows\package.json'
npm WARN saveError EPERM: operation not permitted, open 'C:\Windows\package-lock.json.415733530'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Windows\package.json'
See #1189 for more info
Expected Behavior
install works
Steps To Reproduce
Same as:
Environment
The text was updated successfully, but these errors were encountered: