With WebStorm, you can have several installations of Node.js and switch between them while working on the same project. Make sure the JavaScript and TypeScript and Node.js required plugins are enabled on the Settings | Plugins page, tab Installed, see Managing plugins for details.

Make sure you have Node.js on your computer.

See Node.js with Docker, Node.js via SSH, and Node.js with Vagrant for details. To run a Node.js application remotely, configure it as a remote interpreter. In most cases, WebStorm detects Node.js installations, configures them as interpreters automatically, and adds them to the list where you can select the relevant one. If you want to switch among several Node.js installations, they must be configured as local Node.js interpreters. If you follow the standard installation procedure, in most cases WebStorm detects Node.js itself.Īnd even if you have no Node.js on your computer, you can install it when creating a new Node.js application in the Create New Project dialog, see Creating a new Node.js application below. If you need Node.js only as a local runtime for your application or for managing npm packages, running JavaScript linters, build tools, test frameworks, and so on, just install Node.js. WebStorm integrates with Node.js providing assistance in configuring, editing, running, debugging, testing, profiling, and maintaining your applications.

Then simply this simply allows you to switch your Node versions, also the ability to use install is a lightweight runtime environment for executing JavaScript outside the browser, for example on the server or in the command line. Nvm ls List versions (installed versions are blue)Ī simple install by downloading and running the nvm-setup.zip. It allows you to easily install and manage multiple versions of node. The Node Version Manager. You can find it at Upon this realisation, I completed a quick search and stumbled across a useful tool that can be installed on your Windows machine: The project I was working on required me to update my version of Node.js a pretty straightforward process, until I then returned to an older project that was dependent on an earlier version of Node. Today I’m going to be exploring how to manage multiple installations of Node.js on a windows computer following an issue I recently came across whilst working on a project.

Windows node update