Windows 10 Fall Creators Update - Installing Node.js on Windows Subsystem for Linux (WSL)
Windows just released the windows subsystem for linux feature to the public with its latest windows fall creator update, if you are not familiar with this feature it allows you to run linux binaries natively on windows - F.A.Q.
The feature is not enabled by default and you need to activate it, you can do it via powershell (with admin rights):
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Or you can open: Control-Panel -> Programs -> Turn Windows feature on ro off, and click the “windows subsystem for linux (beta)” button.
Now to install your linux version, again two options, you can either install from Windows store (search linux) or you can turn on developer mode and open it via the command line: Open Settings -> Update and Security -> For developers, and Select the “Developer Mode” radio button.
Installing linux (ubuntu)
For those who are not familiar with linux, fragmentation if part of the fun and there a lot of linux distributions and package management systems for it, the default installation in WSL is ubuntu and I recommend to keep it as it one of the most popular distribution around. If you need different distribution the easiest why is to install it from the windows store.
Run CMD.exe and type:
When you first run the command you’ll encounter the cli based installer wizard, the ubuntu image will automatically download and you’ll be prompt to enter username and password. If you found yourself in need to reset/reinstall the ubuntu machine you can use
CMD> lxrun Performs administrative operations on the LX subsystem Usage: /install - Installs the subsystem Optional arguments: /y - Do not prompt user to accept /uninstall - Uninstalls the subsystem Optional arguments: /full - Perform a full uninstall /y - Do not prompt user to accept /setdefaultuser - Configures the subsystem user that bash will be launched as. If the user does not exist it will be created. Optional arguments: username - Supply the username /y - If username is supplied, do not prompt to create a password /update - Updates the subsystem's package index
That’s it, you’re running ubuntu on windows!
First We’ll start by updating linux, for those of you that are not familiar with linux this require running the process as
root by add the
sudo command before the command we need to execute:
sudo apt-get update sudo apt-get upgrade
You’ll need to enter your user password to proceed, if you prompt just press y (or yes) to continue.
We also need to install some basic build tool for node-gyp - node binaries build tool.
sudo apt-get install build-essential
I do not recommend on the “official” to install node, node rapid development life cycle (and the entire ecosystem for that matter) leads more then often for the need to have tight control over the node binaries version, or more likely to have to project running on different versions of node (such as LTS versions).
NVM tool gives you the ability to install and use multiple version of node, and prevent the (bad) usage of
sudo for running node application, installation is via the command line:
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.5/install.sh | bash
Restart your terminal after install.
Now just install the latest the latest stable version of node:
nvm install stable
To update node just run the command again.
One thing you’ll have to remember when use NVM is that you’ll need to explicitly specify the node version you want to use (installing does it automatically on the end of the install), so next time you’ll login to ubuntu you’ll need to run the command:
nvm use stable
Your windows hard disk drivers are mounted in linux under
/mnt/<drive letter>/ so you can access any folder via linux and run whatever command you need in order to get your project up and running, missing needed tools can be installed via
apt-get for system tools.
IDE terminal integration support is still on its early days, vscode offers support with minimal configuration, guide. If your IDE just point to the executable (like cmd.exe) check if you can point it to