Local package.json exists, but node_modules missing

Question

I am trying to start a Redux application I just cloned from a GitHub repository.

I tried to run it with the following command

npm start

I am getting this error

> react-redux@1.0.0 start /home/workspace/assignment
> webpack-dev-server --config ./configs/webpack/webpack.config.development.js

sh: 1: webpack-dev-server: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! react-redux@1.0.0 start: `webpack-dev-server --config ./configs/webpack/webpack.config.development.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the react-redux@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/.npm/_logs/2018-05-15T16_32_44_571Z-debug.log

Any help will be appreciated

Answer 1

npm start runs a script that the app maker built for easy starting of the app npm install installs all the packages in package.json

run npm install first

then run npm start

Answer 2

Just had the same error message, but when I was running a package.json with:

"scripts": {
    "build": "tsc -p ./src",
}

tsc is the command to run the TypeScript compiler.

I never had any issues with this project because I had TypeScript installed as a global module. As this project didn't include TypeScript as a dev dependency (and expected it to be installed as global), I had the error when testing in another machine (without TypeScript) and running npm install didn't fix the problem. So I had to include TypeScript as a dev dependency ( npm install typescript --save-dev ) to solve the problem.

Answer 3

This issue can also raise when you change your system password but not the same updated on your .npmrc file that exist on path C:\\Users\\user_name , so update your password there too.

please check on it and run npm install first and then npm start.

Answer 4

Working in Grapesjs and get the same error

goto package.json file and check dependencies

1. Removing Don't use plugins or Don't use libraries.

2. npm install

3. npm start

Sometimes not useful install plugins get errors.

Answer 5

Use npm install . I was having a permission issue with running this, due to the closed-nature of my office VPN. This'll solve permission problems...

sudo npm install

In some cases with permissions, when this fails, it emits no error message. In that case, you may want to adjust user permissions with either chown or chmod . Other times, though, when it fails, you'll actually see a legit error message...

npm ERR! network tunneling socket could not be established, statusCode=400

npm ERR! network This is most likely not a problem with npm itself

npm ERR! network and is related to network connectivity.