'node' is not recognized as an internal or external command

# 'node' is not recognized as an internal or external command

The error "'node' is not recognized as an internal or external command, operable program or batch file" occurs for 2 main reasons:

1. Not having Node.js installed on your machine.
2. Not having Node in your system's PATH environment variable.

Copied!
'node' is not recognized as an internal or external command,
operable program or batch file

The term 'node' is not recognized as the name of a cmdlet, function, script file, or operable program.

To install Node and add it to your PATH environment variable:

1. Open the nodejs.org page and download the Windows installer for the LTS (long-term supported) version.

2. Start the installer and click Next on the Welcome screen.

3. Accept the end-user license agreement and click Next.

4. Leave the default destination folder selected and click Next.

5. On the "Custom Setup" screen, click Next. Notice that there is an "Add to PATH" option selected.

6. You can optionally install tools for native modules, otherwise, click Next.

7. On the next screen, click on the Install button.

8. Lastly, click on the Finish button.

9. Make sure to close any existing command prompts and PowerShell instances for the PATH variable to get updated.

10. You can start a new CMD shell and use the node --version command to make sure Node is installed.

Copied!
node --version

If you got the error in Visual Studio Code and restarting VSCode doesn't help, try to click on the trash bin button to restart the terminal.

If the error persists, add Node to your PATH environment variable manually.

# Add Node to your PATH environment variable

To add Node to your PATH environment variable:

1. Click on the Search bar and type "environment variables".
2. Click on "Edit the system environment variables".

3. Click on the "Environment Variables" button.

4. In the "System variables" section, select the "Path" variable and click "Edit".

5. Click on "New" and then click "Browse".

6. Your nodejs directory is most likely under:

• C:\Program Files\nodejs
• or C:\Program Files (x86)\nodejs

7. Next, ensure you also have the path to your npm directory in the PATH as well.

8. Your npm directory is most likely located under %USERPROFILE%\AppData\Roaming\npm, which is the same as C:\Users\YOUR_USER\AppData\Roaming\npm.

Copied!
%USERPROFILE%\AppData\Roaming\npm

# 👇️ same as below (make sure to replace YOUR_USER)
C:\Users\YOUR_USER\AppData\Roaming\npm

If you can't find it, try running the npm config get prefix command.

Copied!
npm config get prefix

9. Add the path to npm and click on "OK" twice to confirm.

10. Close your Command prompt application and then reopen it.

You might also have to restart your PC, but that's not always necessary.

You can start a new CMD shell and use the node --version command to make sure Node is installed and configured properly.

Copied!
node --version

If you got the error in Visual Studio Code and restarting VSCode doesn't help, try to click on the trash bin button to restart the terminal.

If the error persists, try to run CMD or VSCode as an administrator before issuing a node command.

To open CMD as an administrator:

1. Click on the Search bar and type CMD.

2. Right-click on the Command Prompt application and click "Run as administrator".

You can run VSCode as an administrator by right-clicking on VSCode and clicking "Run as administrator".

Try to issue a node command with elevated permissions, e.g. node --version.

# Conclusion

To solve the error "'node' is not recognized as an internal or external command, operable program or batch file", make sure:

1. You have Node.js installed on your machine.
2. You have Node in your system's PATH environment variable.

# Additional Resources

You can learn more about the related topics by checking out the following tutorials:

• eslint is not recognized as an internal or external command
• 'Yarn' is not recognized as an internal or external command
• 'npm' is not recognized as an internal or external command
• npx: command not found Error in Windows, Linux, macOS [Fix]
• 'nvm' is not recognized as an internal or external command
• 'next' is not recognized as an internal or external command