WSL: nvm net.js error after 15031
After updating Windows to 15031 I started seeing the following error when opening a new terminal, because of this line of .bashrc which loads nvm:
export NVM_DIR="/home/ztrange/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
net.js:145
this._handle.open(options.fd);
^
Error: Unknown system error -25: Unknown system error -25, uv_pipe_open
at Error (native)
at new Socket (net.js:145:18)
at createWritableStdioStream (internal/process/stdio.js:156:16)
at process.getStdout [as stdout] (internal/process/stdio.js:10:14)
at module.exports (/home/ztrange/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/npmlog/node_modules/set-blocking/index.js:2:11)
at Object.<anonymous> (/home/ztrange/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/npmlog/log.js:11:1)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v6.9.5 --silent` to unset it.
The part about the config prefix disappeared after I ran the suggested option, but it again returned the same error without the nvm is not compatible
I already tried updating nvm to latest version and installing latest node with nvm but it’s all the same. I also tried installing.
To reproduce I hope it’s enough to install nvm and install node latest
FYI, node works (It was failing but I made it work by removing all installed node versions and reinstalling the latest one) but I haven’t yet seen that node fails unexpectedly. I’m just reporting that it reports that error when loading nvm.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 4
- Comments: 16 (6 by maintainers)
@reybango - I just checked this and the fix made it to the prerelease branch for the 15041 build.
We have identified the issue and the fix has been checked in.
@sebfindling re: avoid, there’s a
pause updatesoption in the advanced options settings, turn it on and you won’t get 15031 build for a month I guess. Hope that helps you out. cheersFYI
Thanks for sharing. The error is likely coming from one of these three operations: