WebStorm Node.js Interpreter Not Configured

How to fix it

Try these in order — the most common fix is first.

1. 1. Select a Node runtime

   Copy steps
   1. Press Ctrl+Alt+S (Cmd+, on macOS) and open Languages & Frameworks | JavaScript Runtime
   2. Make sure Node.js is selected in Preferred runtime
   3. Open the Node runtime list and choose an installation
   Did this fix it? Yes No

2. 2. Add a local Node.js manually

   Copy steps
   1. Click Browse next to the Node runtime list
   2. In the Node.js Runtimes dialog click Add, then Add Local
   3. Select the Node.js installation and click OK
   Did this fix it? Yes No

3. 3. Use the system default with nvm

   Copy steps
   1. In the Node runtime list select node
   2. WebStorm then follows whatever node alias your system points to, so version switches need no settings change
   Did this fix it? Yes No

4. 4. Use WSL Node.js

   Copy steps
   1. Click Browse next to the Node runtime field
   2. Click Add, choose Add WSL
   3. Pick the Linux distribution and enter the path to Node.js
   Did this fix it? Yes No

Symptoms

Node.js features, run configurations, ESLint and Prettier do not work, and the Node runtime field is empty or red.

Why it happens

• Node.js is not installed
• Node.js is installed in a non-default location
• Node version manager changed the active version
• WSL project with a Windows Node path

This guide also covers

• webstorm node interpreter not configured
• webstorm node.js not found
• webstorm nvm node path

Other WebStorm errors

• WebStorm ESLint Not Working
• WebStorm Prettier Not Working
• WebStorm TypeScript Language Service Errors and Slowness
• WebStorm Indexing Takes Forever
• WebStorm High Memory Usage: Increase Heap Size
• WebStorm Debugger Not Attaching or Breakpoints Not Hit
• WebStorm License Activation and Login Problems