Common Node.js Setup Errors and How to Fix Them

Common Node.js Setup Errors and How to Fix Them

Setting up Node.js causes predictable errors. Here are the common ones and how to fix each.

'node' is not recognized

Node.js is not installed or not on your PATH. Install Node.js from the official site or use a version manager like nvm, then reopen your terminal.

'npm' is not recognized

Same as node. npm ships with Node.js, so if npm is not found, Node.js is not installed or not on your PATH. Reinstall or use nvm.

Cannot find module

You are requiring a module that is not installed. Run npm install to install dependencies, or install the specific package with npm install package-name.

Port already in use

Another process is using port 3000 or whichever port you chose. Kill the other process or use a different port. On Mac/Linux, use lsof -i :3000 to find and kill it.

EACCES permission errors

You tried to install globally without permissions, or your node_modules folder has wrong ownership. Use nvm to avoid global permission issues, or fix folder ownership rather than using sudo.

SyntaxError: Cannot use import statement outside a module

You are using import instead of require in a CommonJS project. Either switch to require, or set 'type': 'module' in package.json to enable ES modules.

The Takeaway

Common Node.js setup errors include node and npm not recognized, cannot find module, port already in use, EACCES permissions, and import statement errors. Each has a clear fix once you recognize the symptom.