# Node.js Runtimes Dialog

> **TL;DR**
> Required plugins:
>
>
>
> JavaScript and TypeScript -   the plugin is bundled with CLion and enabled by default.
>
>
>
> Node.js (only for developing Node.js applications) -   install the plugin on the Settings | Plugins page, tab Marketplace.

The following Node.js versions are supported in CLion 2023.3 and later:

* Node.js 22 - the Active Long Term Supported (LTS) version

* Node.js 24 - the current version

Learn more from [Supported Node.js versions](supported-node-js-versions.html).

Use this dialog to configure a [local](developing-node-js-applications.html#ws_node_configure_local_node_interpreter) or [remote](null) Node.js runtime or a [Node.js on Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/about).

The term local Node.js runtime denotes a Node.js installation on your computer. The term remote Node.js runtime denotes a Node.js installation on a remote host or in a virtual environment.

## Before you start

Procedure:

1. Download and install [Node.js](http://nodejs.org/#download).

2. Install and enable and enable the Node.js plugin on the Settings | Plugins page, tab Marketplace, as described in [Installing plugins from
JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo).

3. If you are going to configure a runtime,   install the Node.js Remote Interpreter plugin  in `Settings | Plugins`  as described in [Installing plugins from JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo).

## Open the Node.js Runtimes dialog

The way you get to the Node.js Runtimes dialog depends on the type of runtime you want to use.

Procedure: You need a local or a WSL Node.js runtime

1. Open the Settings dialog (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS))) , go to `Languages & Frameworks | JavaScript Runtime`.

2. Make sure that Node.js is selected in the Preferred runtime field.

3. Click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) next to the Node runtime field.

![Open the Node.js Runtimes dialog from Settings](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_node_interpreter_from_settings.animated.gif)

Procedure: You need a remote Node.js runtime

1. Go to `Run | Edit Configurations`, then select the required Node.js run/debug configuration. For more information, refer to [Working with run/debug configurations](run-debug-configuration.html).

2. In the [Run/Debug Configuration: Node.js dialog](run-debug-configuration-node-js.html), click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) next to the Node runtime field.

![Open the Node.js Runtimes dialog from Node.js run configuration](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_node_interpreter_from_rc.animated.gif)

> **Warning:**
> Configured remote runtimes will not show up if you later open the Node.js Interpreters dialog from Settings (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)).

## Configure Node.js runtimes

The Node.js Runtimes dialog lists all the configured local, WSL, and remote Node.js runtimes that are available in the current context.

You can open the dialog [from the
Node.js page](#ws_node_interpreters_dialog_open_from_settings) or [from  a Node
.js run configuration](#ws_node_interpreters_dialog_open_from_rc).

Use ![the Add button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg), ![the Remove button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg), and ![the Edit button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.edit.svg) to add and remove existing Node.js configurations as well as create new ones based on their settings.

|  ![the Add button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.add.svg)  |  Add  |    Click this button to add a new Node.js runtime to the list and select Add Local, Add Remote, or Add WSL from the list.                           Depending on your choice, select the relevant local Node.js installation, or configure a remote runtime in the [Configure Node.js Remote                             Runtime dialog](null), or specify the Linux distribution you’re using and the path to Node.js in the Add WSL Node Runtime dialog.     |
|  ![the Remove button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.remove.svg)  |  Delete  |  Click this button to remove the selected runtime from the list.  |
|  ![the Edit button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.edit.svg)  |  Edit  |  Click this button to create a new runtime with the settings copied from the selected one.  |