Скачать или смотреть Resolving the node: command not found Error with npm Path Issues

Encountering the frustrating `node: command not found` error? Learn how to resolve this issue by fixing your npm path settings in a few simple steps!
---
This video is based on the question https://stackoverflow.com/q/62362389/ asked by the user 'codejs' ( https://stackoverflow.com/u/10965250/ ) and on the answer https://stackoverflow.com/a/62365724/ provided by the user 'codejs' ( https://stackoverflow.com/u/10965250/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: node: command not found with two /npm/npm in path

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Fix the node: command not found Error in Your Terminal

If you are working with Node.js and npm, encountering the node: command not found error can be particularly frustrating, especially when you just want to get your application running. This error typically indicates that the terminal cannot find the Node.js command, which is usually caused by incorrect paths configured in the environment variables. Today, we'll break down how to solve this issue step-by-step.

Understanding the Problem

You might start your project expecting to run commands like npm start or node server.js, only to be greeted by the error message, "node: command not found."

Key Symptoms

The terminal outputs:

[[See Video to Reveal this Text or Code Snippet]]

In your path, you notice something peculiar:

[[See Video to Reveal this Text or Code Snippet]]

Possible confusion arises from seeing two /npm directories in your path.

Hidden Directories

If you've checked your AppData folder and found it empty, it's possible that certain folders are hidden by default in your operating system.

Solution Steps

To fix this issue, you need to correctly specify the paths for Node.js and npm in your environment variables. Here’s how you can do that:

Step 1: Locate Node.js Installation

Verify Node.js Installation:
Make sure Node.js is installed on your computer. Typically, it installs in:

[[See Video to Reveal this Text or Code Snippet]]

Check npm Location:
Navigate to C:\Program Files\nodejs\node_modules\npm to ensure that npm is available in that directory.

Step 2: Set Environment Variables

To configure your PATH variable, follow these steps:

Search for Environment Variables:
In Windows Search, type "Environment Variables" and select Edit the system environment variables.

Edit System Variables:
Click on the Environment Variables button.

Add New Variable Paths:
In the System variables section, locate the Path variable, select it, and click Edit. Here, you need to add the following paths:

C:\Program Files\nodejs

C:\Program Files\nodejs\node_modules\npm\bin

C:\Program Files\nodejs\node_modules\npm

C:\Windows\System32

Save Changes:
Click OK to save your changes and exit from all dialogs.

Step 3: Verify the Fix

Once the paths are added, open a new terminal window and type the following commands to confirm the installation:

[[See Video to Reveal this Text or Code Snippet]]

Both commands should return the installed versions of Node.js and npm, indicating that they are correctly configured.

Conclusion

By carefully updating your environment variables, you can resolve the annoying node: command not found error that arises with npm. It’s important to pay attention to the paths you include in your system settings. While the exact requirements may vary from system to system, adding the necessary paths and ensuring your installation is correct will set you up for success in your Node.js projects.

If you still face issues, consider checking for hidden files or reinstalling Node.js and npm. Happy coding!