Set up your Node.js development environment with WSL 2
The following is a step-by-step guide to help you get your Node.js development environment set up using Windows Subsystem for Linux (WSL).
We recommend that you install and run the updated WSL 2, as you will benefit from significant improvements in performance speed and system call compatibility, including the ability to run Docker Desktop. Many npm modules and tutorials for Node.js web development are written for Linux users and use Linux-based packaging and installation tools. Most web apps are also deployed on Linux, so using WSL 2 will ensure you have consistency between your development and production environments.
If you are committed to using Node.js directly on Windows, or plan to use a Windows Server production environment, see our guide to set up your Node.js development environment directly on Windows.
Install WSL 2
To enable and install WSL 2, follow the steps in the WSL install documentation. These steps will include choosing a Linux distribution (for example, Ubuntu).
Once you have installed WSL 2 and a Linux distribution, open the Linux distribution (it can be found in your Windows start menu) and check the version and codename using the command:
We recommend updating your Linux distribution regularly, including immediately after you install, to ensure you have the most recent packages. Windows doesn't automatically handle this update. To update your distribution, use the command:
sudo apt update && sudo apt upgrade.
Install Windows Terminal (optional)
The new Windows Terminal enables multiple tabs (quickly switch between multiple Linux command lines, Windows Command Prompt, PowerShell, Azure CLI, etc), create custom key bindings (shortcut keys for opening or closing tabs, copy+paste, etc.), use the search feature, and custom themes (color schemes, font styles and sizes, background image/blur/transparency). Learn more.
Get Windows Terminal in the Microsoft Store: By installing via the store, updates are handled automatically.
Once installed, open Windows Terminal and select Settings to customize your terminal using the
Install nvm, node.js, and npm
There are multiple ways to install Node.js. We recommend using a version manager as versions change very quickly. You will likely need to switch between multiple versions based on the needs of different projects you're working on. Node Version Manager, more commonly called nvm, is the most popular way to install multiple versions of Node.js. We will walk through the steps to install nvm and then use it to install Node.js and Node Package Manager (npm). There are alternative version managers to consider as well covered in the next section.
It is always recommended to remove any existing installations of Node.js or npm from your operating system before installing a version manager as the different types of installation can lead to strange and confusing conflicts. For example, the version of Node that can be installed with Ubuntu's
apt-get command is currently outdated. For help with removing previous installations, see How to remove nodejs from ubuntu.)
- Open your Ubuntu 18.04 command line.
- Install cURL (a tool used for downloading content from the internet in the command-line) with:
sudo apt-get install curl
- Install nvm, with:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
At the time of publication, NVM v0.35.3 was the most recent version available. You can check the GitHub project page for the latest release of NVM, and adjust the above command to include the newest version.
Installing the newer version of NVM using cURL will replace the older one, leaving the version of Node you've used NVM to install intact. For example:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.36.0/install.sh | bash
To verify installation, enter:
command -v nvm...this should return 'nvm', if you receive 'command not found' or no response at all, close your current terminal, reopen it, and try again. Learn more in the nvm github repo.
List which versions of Node are currently installed (should be none at this point):
Install the current release of Node.js (for testing the newest feature improvements, but more likely to have issues):
nvm install node
Install the latest stable LTS release of Node.js (recommended):
nvm install --lts
List what versions of Node are installed:
nvm ls...now you should see the two versions that you just installed listed.
Verify that Node.js is installed and the currently default version with:
node --version. Then verify that you have npm as well, with:
npm --version(You can also use
which npmto see the path used for the default versions).
To change the version of Node.js you would like to use for a project, create a new project directory
mkdir NodeTest, and enter the directory
cd NodeTest, then enter
nvm use nodeto switch to the Current version, or
nvm use --ltsto switch to the LTS version. You can also use the specific number for any additional versions you've installed, like
nvm use v8.2.1. (To list all of the versions of Node.js available, use the command:
If you are using NVM to install Node.js and NPM, you should not need to use the SUDO command to install new packages.
Alternative version managers
While nvm is currently the most popular version manager for node, there are a few alternatives to consider:
- n is a long-standing
nvmalternative that accomplishes the same thing with slightly different commands and is installed via
npmrather than a bash script.
- fnm is a newer version manager, claiming to be much faster than
nvm. (It also uses Azure Pipelines.)
- Volta is a new version manager from the LinkedIn team that claims improved speed and cross-platform support.
- asdf-vm is a single CLI for multiple languages, like ike gvm, nvm, rbenv & pyenv (and more) all in one.
- nvs (Node Version Switcher) is a cross-platform
nvmalternative with the ability to integrate with VS Code.
Install your favorite code editor
We recommend using Visual Studio Code with the Remote-WSL Extension for Node.js projects. This splits VS Code into a “client-server” architecture, with the client (the VS Code user interface) running on your Windows operating system and the server (your code, Git, plugins, etc) running "remotely" on your WSL Linux distribution.
This “remote” scenario is a bit different than you may be accustomed to. WSL supports an actual Linux distribution where your project code is running, separately from your Windows operating system, but still on your local machine. The Remote-WSL extension connects with your Linux subsystem as if it were a remote server, though it’s not running in the cloud… it’s still running on your local machine in the WSL environment that you enabled to run alongside Windows.
- Linux-based Intellisense and linting is supported.
- Your project will automatically build in Linux.
- You can use all your extensions running on Linux (ES Lint, NPM Intellisense, ES6 snippets, etc.).
Terminal-based text editors (vim, emacs, nano) are also helpful for making quick changes from right inside your console. (This article does a nice job explaining the difference and a bit about how to use each.)
Some GUI editors (Atom, Sublime Text, Eclipse) may run into trouble accessing the WSL shared network location (\wsl$\Ubuntu\home) and will try to build your Linux files using Windows tools, which may not be what you want. The Remote-WSL Extension in VS Code will handle this compatibility for you.
To install VS Code and the Remote-WSL Extension:
Download and install VS Code for Windows. VS Code is also available for Linux, but Windows Subsystem for Linux does not support GUI apps, so we need to install it on Windows. Not to worry, you'll still be able to integrate with your Linux command line and tools using the Remote - WSL Extension.
If you already have VS Code installed, you need to ensure that you have the 1.35 May release or later in order to install the Remote - WSL Extension. We do not recommend using WSL in VS Code without the Remote-WSL extension as you will lose support for auto-complete, debugging, linting, etc. Fun fact: This WSL extension is installed in $HOME/.vscode-server/extensions.
Helpful VS Code Extensions
While VS Code comes with many features for Node.js development out of the box, there are some helpful extensions to consider installing available in the Node.js Extension Pack. Install them all or pick and choose which seem the most useful to you.
To install the Node.js extension pack:
Open the Extensions window (Ctrl+Shift+X) in VS Code.
The Extensions window is now divided into three sections (because you installed the Remote-WSL extension).
- "Local - Installed": The extensions installed for use with your Windows operating system.
- "WSL:Ubuntu-18.04-Installed": The extensions installed for use with your Ubuntu operating system (WSL).
- "Recommended": Extensions recommended by VS Code based on the file types in your current project.
In the search box at the top of the Extensions window, enter: Node Extension Pack (or the name of whatever extension you are looking for). The extension will be installed for either your Local or WSL instances of VS Code depending on where you have the current project opened. You can tell by selecting the remote link in the bottom-left corner of your VS Code window (in green). It will either give you the option to open or close a remote connection. Install your Node.js extensions in the "WSL:Ubuntu-18.04" environment.
A few additional extensions you may want to consider include:
- Debugger for Chrome: Once you finish developing on the server side with Node.js, you'll need to develop and test the client side. This extension integrates your VS Code editor with your Chrome browser debugging service, making things a bit more efficient.
- Keymaps from other editors: These extensions can help your environment feel right at home if you're transitioning from another text editor (like Atom, Sublime, Vim, eMacs, Notepad++, etc).
- Settings Sync: Enables you to synchronize your VS Code settings across different installations using GitHub. If you work on different machines, this helps keep your environment consistent across them.
Set up Git (optional)
To set up Git for a NodeJS project on WSL, see the article Get started using Git on Windows Subsystem for Linux in the WSL documentation.
You now have a Node.js development environment set up. To get started using your Node.js environment, consider trying one of these tutorials: