# JavaScript Runtimes > **TL;DR** > `File | Settings | Languages & Frameworks | JavaScript Runtime` for Windows and Linux > > > > `IntelliJ IDEA | Settings | Languages & Frameworks | JavaScript Runtime` for macOS > > > > `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)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) ![the Settings icon](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.settings.svg) > > > > Required plugins: > > > > JavaScript and TypeScript -  the plugin is bundled with IntelliJ IDEA and enabled by default. > > > > Node.js (only for developing Node.js applications) -  install the plugin on the Settings | Plugins page, tab Marketplace. The plugin is available only in IntelliJ IDEA with the Ultimate subscription. ## Preferred runtime In this area, choose the runtime to use. The set of available runtimes depends on the plugins installed. ## Package manager In this field, choose the package manager (npm, Yarn, pnpm, bun) for the current project. IntelliJ IDEA uses the `npm`, `yarn`, `pnpm`, and `bun` aliases for the current system paths to these managers. To use a custom installation, click Select, and select the installation folder of the relevant package manager. For more information, refer to [Configuring a package manager for a project](installing-and-removing-external-software-using-node-package-manager.html#ws_npm_yarn_configure_package_manager). By default, IntelliJ IDEA suggests npm. However, if you open a project with a `yarn.lock` file and Yarn is installed on your computer, IntelliJ IDEA automatically changes the package manager for this project to Yarn. Accordingly, if you open a project with a `pnpm-lock` file and pnpm is installed on your computer, IntelliJ IDEA automatically changes the package manager for this project to pnpm. You can also [set Yarn 1 or pnpm as default IntelliJ IDEA package manager](installing-and-removing-external-software-using-node-package-manager.html#ws_npm_yarn_set_yarn_default). ## Node.js In this area, specify the Node.js runtime to use in your project and enable Node.js-specific coding assistance. On how to work with Node.js, refer to the [developing the Node.js applications](developing-node-js-applications.html) section. ### Node.js runtime In this field, specify the default Node.js runtime for the current project. IntelliJ IDEA automatically uses it every time you select the `Project` alias from Node runtime lists, for example, when creating run/debug configurations. Select a configured runtime from the list or click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) and configure a new one in the dialog that opens as described in [Configuring a local Node.js runtime](developing-node-js-applications.html#ws_node_configure_local_node_interpreter). If you select node, the [system Node.js version](developing-node-js-applications.html#ws_node_version) is used. You can select or configure a runtime of one of the following types: * Local interpreter — a Node.js installed on your computer. Learn more from [Configuring a local Node.js runtime](developing-node-js-applications.html#ws_node_configure_local_node_interpreter). * [Node.js on Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/about), learn more from [Using Node.js on Windows Subsystem for Linux](developing-node-js-applications.html#ws_node_wsl). * Remote interpreter — a Node.js on a remote host or in a virtual environment. Learn more from [Node.js with Docker](node-with-docker.html), [Node.js via SSH](node-via-ssh.html), and [Node.js with Vagrant](null). ### Version This read-only field shows the version of the selected Node.js. The following Node.js versions are supported in IntelliJ IDEA 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) ### Coding assistance for Node.js Select this checkbox to configure the Node.js Core module sources as a [JavaScript library](configuring-javascript-libraries.html#ws_js_libraries_node_js_core) and associate it with your project. As a result, IntelliJ IDEA provides code completion, reference resolution, validation, and debugging capabilities for `fs`, `path`, `http`, and other parts of Node.js that are compiled into the Node.js binary. When the configuration is completed, IntelliJ IDEA displays information about the currently configured version. If you need code completion for Node.js APIs only in some parts of your project, you can configure that using the Manage scopes link. In the [Usage dialog](null) that opens, click the relevant directories and for each of them select the configured Node.js Core library from the list. Learn more from [Configuring the scope of a library](configuring-javascript-libraries.html#ws_js_configuring_js_libs_change_scope). ## Bun > **Note:** > The area is available only when the Bun plugin is installed on the Settings | Plugins page, tab Marketplace, as described in [Installing plugins from JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo). In this area, specify the path to the Bun executable file. The path to the Bun executable file defaults to your `PATH` environment variable, so if you leave the Bun field empty, the debugger attempts to detect the Bun executable file automatically. ## Deno > **Note:** > The area is available only when the Deno plugin is installed on the Settings | Plugins page, tab Marketplace, as described in [Installing plugins from JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo). ## See also ### Language and Framework-Specific Guidelines [npm, pnpm, and Yarn](installing-and-removing-external-software-using-node-package-manager.html) [Node.js](developing-node-js-applications.html)