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

creationix nvm on windows 10 - it's possible now #1714

Closed
Bennit opened this issue Jan 26, 2018 · 2 comments
Closed

creationix nvm on windows 10 - it's possible now #1714

Bennit opened this issue Jan 26, 2018 · 2 comments

Comments

@Bennit
Copy link

Bennit commented Jan 26, 2018

Using linux subsystem for windows 10 + ubuntu shell (installed through windows store) I was able to install nvm using the curl command , install a version of node and run node code.

Perhaps the doc can be updated with this information as I prefer this version of nvm over the alternatives mentioned in the readme, I suppose there will be more people that share this feeling.

One remark though -- while installing I encountered following error in the console, which seems to be perfectly ignore-able as it guess it only affects bash completion:

=> Appending nvm source string to /home/bcorne/.bashrc
=> Appending bash_completion source string to /home/bcorne/.bashrc
net.js:200
    this._handle.open(options.fd);
                 ^

Error: EINVAL: invalid argument, uv_pipe_open
    at new Socket (net.js:200:18)
    at createWritableStdioStream (internal/process/stdio.js:164:16)
    at process.getStdout [as stdout] (internal/process/stdio.js:14:14)
    at console.js:243:38
    at NativeModule.compile (bootstrap_node.js:596:7)
    at Function.NativeModule.require (bootstrap_node.js:541:18)
    at setupGlobalConsole (bootstrap_node.js:310:41)
    at startup (bootstrap_node.js:70:7)
    at bootstrap_node.js:608:3
=> Close and reopen your terminal to start using nvm or run the following to use it now:

Not 100% sure yet about how far the linux modules for node are compatible with the (limited) linux subsystem of win10 - so it's worth giving it a try and sharing your issues.

@ljharb
Copy link
Member

ljharb commented Jan 26, 2018

It's been possible for awhile :-) Since the linux subsystem claims to be POSIX compliant, and nvm requires POSIX, please do file issues if you see any problems.

In that specific case, I'd file an issue on WSL itself about that bash_completion file.

@WingGao
Copy link

WingGao commented Jun 25, 2019

I solved this problem by remove the windows PATH in WSL.
The method is here microsoft/WSL#1493, and it works fine.

@ljharb ljharb closed this as completed Jan 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants