501

I'm trying to learn react, so I have this sample code for the full-stack react voting app, and I am trying to get it to work but after running npm install followed by npm start I receive the following error when I run npm start can anyone help me with this issue:

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "server"
npm ERR! node v7.5.0
npm ERR! npm  v4.3.0
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] server: `live-server --public --    
host=localhost --port=3000 --middleware=./disable-browser-cache.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] server script 'live-server --
public --host=localhost --port=3000 --middleware=./disable-browser- 
cache.js'.
npm ERR! Make sure you have the latest version of node.js and npm  
installed.
npm ERR! If you do, this is most likely a problem with the voting_app  
package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     live-server --public --host=localhost --port=3000 --  
middleware=./disable-browser-cache.js
npm ERR! You can get information on how to open an issue for this  
project with:
npm ERR!     npm bugs voting_app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls voting_app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/ItsMeMrLi/.npm/_logs/2017-02-17T22_48_03_581Z-
debug.log

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.5.0
npm ERR! npm  v4.3.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm run server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'npm run server'.
npm ERR! Make sure you have the latest version of node.js and npm 
installed.
npm ERR! If you do, this is most likely a problem with the voting_app    
package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run server

npm ERR! You can get information on how to open an issue for this   
project with:
npm ERR!     npm bugs voting_app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls voting_app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/ItsMeMrLi/.npm/_logs/2017-02-17T22_48_03_655Z-
debug.log

Here is my package.json:

{
  "name": "voting_app",
  "version": "1.1.0",
  "author": "Fullstack.io",
  "scripts": {
    "go": "open http://localhost:3000; npm run server",
    "e2e": "nightwatch",
    "test": "./node_modules/.bin/concurrently -k 'npm run server' 'npm  
run e2e'",
    "start": "npm run server",
    "server": "live-server public --host=localhost --port=3000 --  
middleware=./disable-browser-cache.js"
  },
  "private": true,
  "devDependencies": {
  "concurrently": "2.2.0",
  "live-server": "git://github.com/acco/live-server.git"
},
  "dependencies": {
  "semantic-ui": "git://github.com/Semantic-Org/Semantic-
  UI.git#27d58a01793b66318478fbc5b6676804d22d065d"
  }
}

And finally my log file:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/ItsMeMrLi/Downloads/fullstack-react-code/voting_app/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/Users/ItsMeMrLi/.rvm/gems/ruby-2.3.1/bin:/Users/ItsMeMrLi/.rvm/gems/ruby-2.3.1@global/bin:/Users/ItsMeMrLi/.rvm/rubies/ruby-2.3.1/bin:/Users/ItsMeMrLi/.cargo/bin:/usr/local/Cellar/smlnj/110.74/libexec/bin:/usr/local/bin:/Users/ItsMeMrLi/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Downloads/geckodriver:/usr/local/bin:/Users/ItsMeMrLi/.rvm/bin
10 verbose lifecycle [email protected]~start: CWD: /Users/ItsMeMrLi/Downloads/fullstack-react-code/voting_app
11 silly lifecycle [email protected]~start: Args: [ '-c', 'npm run server' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `npm run server`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:192:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:192:7)
14 verbose stack     at maybeClose (internal/child_process.js:890:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /Users/ItsMeMrLi/Downloads/fullstack-react-code/voting_app
17 error Darwin 16.4.0
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
19 error node v7.5.0
20 error npm  v4.3.0
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start: `npm run server`
23 error Exit status 1
24 error Failed at the [email protected] start script 'npm run server'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the voting_app package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error     npm run server
24 error You can get information on how to open an issue for this project with:
24 error     npm bugs voting_app
24 error Or if that isn't available, you can get their info via:
24 error     npm owner ls voting_app
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]
2
  • 2
    Make sure you also have space left on the drive.
    – Mircea
    Commented Jul 25, 2018 at 12:44
  • If you were like me you were following the FullStack React book. When you posted this question it is very likely you omitted the vital part of the message preceding what you posted. See here stackoverflow.com/a/65399700/495157 (relative path of disable-browser-cache.js). ./ -> ../.. github.com/tapio/live-server/issues/245
    – JGFMK
    Commented Dec 21, 2020 at 20:59

51 Answers 51

554

Step 1: $ npm cache clean --force

Step 2: Delete node_modules by $ rm -rf node_modules (rmdir /S /Q node_modules in windows) folder or delete it manually by going into the directory and right-click > delete / move to trash. If you are not updating your packages you can delete the package-lock.json file too.

Step 3: npm install

To start again, $ npm start

This worked for me. Hope it works for you too.

While above suggests re-creating package-lock.json file, ensure package-lock.json file exists to begin with, and is tracked by VCS/Git (if the project has VCS).

PS: Still if it's still there, kindly check the error it is displaying in red and act accordingly. This error is specific to node.js environment.

7
  • 40
    heads up be careful when using rm -rf
    – Suhayb
    Commented Nov 25, 2018 at 17:56
  • 39
    For Step 2 in Windows you can do rd /s /q "node_modules"in cmd or rm -r "node_modules" in PowerShell Source Commented Dec 5, 2018 at 13:14
  • 2
    In my case deleting node_modules helped, but this folder that was one level up to the project. npm cache clean --force was causing weird behavior instead and was misleading. Before I deleted this directory I also deleted local repository for this project and cloned it again, not sure if it was helping though since the action I described solved the situation finally.
    – Lukasz
    Commented May 29, 2019 at 10:31
  • If that doesn't work, you can always command another npx create-react-app spare, and copy node_modules over to project appropriately.(USER FRIENDLY WAY)
    – Goku
    Commented Oct 22, 2020 at 7:06
  • 1
    for step 2, I think you can use npm ci Commented Feb 18, 2021 at 10:10
166

Cleaning Cache and Node_module are not enough. Follow this steps:

  • npm cache clean --force
  • delete node_modules folder
  • delete package-lock.json file
  • npm install

It works for me like this.

7
  • 24
    Fixed for me using npm cache verify instead of deleting the entire cache.
    – Jared
    Commented Oct 7, 2018 at 2:18
  • 5
    I think the most important thing is delete the package-lock.json file, before try this, I've tried many ways all cannot fix the error.
    – BobGao
    Commented Feb 6, 2019 at 8:41
  • 50
    The fact that you can fix ANYTHING by simply deleting an autogenerated build artifact is everything that is wrong with the JS universe... If it wasn't for this stackoverflow entry I would have been S.O.L. here as there was no actionable error I could discern in the build log!
    – pmarreck
    Commented Jun 21, 2019 at 19:26
  • Most imp is deleting package-lock.json
    – Yusuf
    Commented Jun 27, 2020 at 15:51
  • If the error still exist after the above solutions, increase the no of listeners. github.com/guard/listen/wiki/…
    – shamila
    Commented Sep 17, 2020 at 9:36
44

I resolve this error running following code

npm cache clean

then delete node_modules directory from my project structure manually or with following command

rm -rf node_modules

After That install dependencies again using

npm install
5
  • 10
    It would really help if you can elaborate the answer for the beginners like me. Brevity is good but doesn't help always. Thank you. Commented Jun 4, 2017 at 7:58
  • 1
    npm run clean is no command. But, still you idea worked. I deleted and reinstalled..and booom... it started working.. thanks
    – Tarunn
    Commented Jun 20, 2017 at 9:49
  • Just the last instruction "npm install" worked in my similar case. Commented Jan 17, 2020 at 7:05
  • had that problem with Nuxt.js after copy / paste my code from desktop to server. not it works thanks
    – Ilijanovic
    Commented Jul 16, 2020 at 21:16
  • npm cache clean then npm cache verify then rm -rf node_modules then npm install Commented May 3, 2021 at 20:01
34

first i ran:

npm run clean

(even though it came with errors)

Then i deleted the node_modules folder and ran

npm install

This seems to have solved the problem.

1
  • npm ERR! missing script: clean
    – Omar Trkzi
    Commented Dec 10, 2023 at 15:44
33

I was getting similar error messages on a 16.04 Ubuntu instance with DigitalOcean while running npm run build on an app made with create-react-app (link). I upgraded the instance from 512MB RAM to 1GB ($5/mo to $10/mo) and then the script was able to run.

I post this here to point out that you may get this error due to resource limitations, which I didn't really see explained elsewhere on issue pages and SO answers. And nothing I saw in the error logs pointed me in this direction.

3
  • 2
    You are completely right ! Nothing point me in this direction too, and it was a bug due to resource limitations... Ty
    – Kubadev
    Commented Jul 31, 2019 at 14:31
  • 1
    Yeah I was getting similar issue compiling Laravel-mix on EC2 t3a.nano instance. Seems to be lack of memory. Resolved on a larger instance. Commented May 16, 2020 at 22:08
  • Before you do this, you might want to try to reboot your server first: digitalocean.com/community/questions/… For me that was sufficient already :)
    – jumelet
    Commented Nov 20, 2020 at 0:20
23

Change access in node_modules directory

chmod -R a+rwx ./node_modules 
0
20

This solution is for Windows users.

You can open the node.js installer and give the installer some time to compute space requirements and then click next and click remove. This will remove node.js from your computer and again reopen the installer and install it in this path - C:\Windows\System32

or

Cleaning Cache and Node_module will work. Follow this steps:

  • npm cache clean --force
  • delete node_modules folder
  • delete package-lock.json file
  • npm install
3
  • Recently I updated my node on windows to 12.X.X, I see the same errors, Cleaning the cache didn't help. Any other possible solutions?
    – chris
    Commented Jul 29, 2020 at 17:59
  • @chris Did you try reinstalling in the node path mentioned in my answer.
    – user13769010
    Commented Aug 19, 2020 at 13:48
  • @chris the purpose for the first fix was not to update it was to reinstall in the path C:\Windows\System32
    – user13769010
    Commented Aug 31, 2020 at 6:45
13

Faced this exact problem,

for me it worked by deleting package-lock.json and re-running npm install

If that doesn't resolve it try

  1. delete package-lock.json
  2. npm cache clean --force
  3. npm install
  4. npm start
11

Delete node_modules and package-lock.json, and then run npm install. It worked perfectly here(run command below inside project root):

rm -rf node_modules && rm ./package-lock.json && npm install
0
11

I was getting this npm ERR! code ELIFECYCLE error while running a build. Clearing the cache and removing the package-lock.json files did not fix it.

In my case there was an Angular build running on a Docker image that was causing this. The root cause turned out to be running the build on Docker in MacOS, which runs the Docker inside a Linux VM, and has by default 2GB memory allocated.

Giving Docker more memory fixed this issue for me. Have to say, the error message could have been quite a bit more clear..

A helpful answer for me was Call retries were exceeded exception while ng build

6

workaround: Remove the lock file.

rm .\package-lock.json

source: https://github.com/mapbox/node-pre-gyp/issues/298 (floriantraber)

0
6

React Application: For me the issue was that after running npm install had some errors.

I've went with the recommendation npm audit fix. This operation broke my package.json and package-lock.json (changed version of packages and and structure of .json).

THE FIX WAS:

  • Delete node_modules
  • Run npm install
  • npm start

Hope this will be helpfull for someone.

5
npm install --unsafe-perm

worked for me. See https://docs.npmjs.com/. The --unsafe-perm parameter lets you run the scripts from the package instalation as root. The problem in my case was that some depandencies failed to install.

1
  • Thanks, I had a problem with "node-pre-gyp", the "--unsafe-perm" solved my installation problem. Commented Oct 10, 2020 at 13:33
5

This solution fixed the error in Win10.

Please install globally npm install -g node-pre-gyp

1
  • Please explain in more detail why you believe this is the solution. Also, give some consideration to others and give a description of what node-pre-gyp is and why this is the answer on Windows 10. Commented Nov 7, 2022 at 20:43
5

i tried to solve this problem with this way

rm -rf node_modules && rm ./package-lock.json && npm install

But for me its not work. I just restart my machine and its working perfectly.
Am Linux user ,Machine HP.

1
  • I was using an Hp running windows and wsl and this worked for me Commented Mar 23, 2021 at 5:30
5

I just wanted to do run npm run dist to apply some changes for SCSS files, but after hours of suffering, here's what worked for me:

  1. npm cache clean --force
  2. delete node_modules folder
  3. delete package-lock.json file
  4. sudo npm install npm@latest -g this will upgrade npm to latest version
  5. npm audit fix --force
  6. npm upgrade --force
  7. npm install

After these I could finally compile SCSS files successfully with npm run dist.

4

A possibly unexpected cause: you use Create React App with some warnings left unfixed, and the project fails on CI (e.g. GitLab CI/CD):

Treating warnings as errors because process.env.CI = true.
[ ... some warnings here ...]
npm ERR! code ELIFECYCLE
npm ERR! errno 1

Solution: fix yo' warnings!

Alternative: use CI=false npm run build

See CRA issue #3657

(Ashamed to admit that it just happened to me; did not see it until a colleague pointed it out. Thanks Pascal!)

4

I recommend you update your node version to the latest node version recommended by your application or for short update your node version. I encountered this same problem using node version 11.1 but my application was recommending atleast version 10.x.x or 12.x.x I tried all the suggested reply on this thread but non seemed to work for me untill only when i updated my node version to the recommended latest version .i.e. version 12.16.3 then my application ran. enter image description here

1
  • Updating npm from 6.14.11 to 8.5.0 fixed the problem in my case although it now reports new ones :)
    – burkay
    Commented Apr 9, 2022 at 17:43
4

In my case, I actually ran into this error "code ELIFECYCLE" in a Jenkins job. I tried to clean npm cache but it didn't work and also checked the memory of the Jenkins build server which looks okay. Then, I found the compiling of the react project actually failed in Jenkins but not in my local or when manually running the build on the Jenkins build server, and Jenkins also mentioned "Treating warnings as errors because process.env.CI = true". It looks like the warnings in my project cause the error on Jenkins. Therefore, I changed CI to true in the Jenkins job for now. That actually fixed the build error of Jenkins before I cleared those warnings.

3

Check for port availability as well if you encounter below message :

Error: listen EACCES 127.0.0.1:8080

at Object._errnoException (util.js:999:13)
at _exceptionWithHostPort (util.js:1020:20)
at Server.setupListenHandle [as _listen2] (net.js:1362:19)
at listenInCluster (net.js:1420:12)
at GetAddrInfoReqWrap.doListen [as callback] (net.js:1535:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:102:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
1
  • For me it was the port that was not available. All I had to do was change the port number and it worked. Commented Apr 15, 2020 at 20:05
3

I'm using ubuntu 18.04 LTS release and I faced the same problem I tried to clean cache as above suggestions but it didn't work for me. However, I found another solution.

echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches

npm start

I run this command and it started to work

2

Try to reinstall the cli package globally. In my case, I was trying to test a Vue.js tutorial when I get the same error message. The other thing I did was run the vue command again but this time using webpack-simple and that is why I am not sure wich one solved the problem but now it is working.

2

I've been bothered by this issue for a long time. For me, the version of node was the problem.

My npm and node were 6.1.0 and 8.11.3, respectively. However, I didn't realize that I had updated my node accidentally to 12.*.*.

It then began to install GCX stuff whenever npm i, which was unnecessary before.

I downgraded my node to 8 and it worked!

2

The port is probably being used by another application, try listing and see if it's your application:

lsof -i:8080

You can kill the process of this port:

lsof -ti:8080 | xargs kill

0
2

I did follow steps, it works:

1.

npm cache clean --force
  1. remove the package-lock.json file

  2. restart my WebStorm

2

Usually killall node command fixes mine.

4
1

Resolved like this:

# chown -R <user>: node_modules
1

In my case, I had checked out a different branch with a new library on it. I fixed my issue by only running npm install without doing anything else. I was confused why I was getting ELIFECYCLE error when the port was not being used, but it must have been because I did not have the library installed. So, you might not have to delete node_modules to fix the issue.

1

Make sure to use the latest npm version while installing packages using npm.

While installing JavaScript, mention the latest version of NodeJS. For example, while installing JavaScript using devtools, use the below code:

devtools i --javascript nodejs:10.15.1

This will download and install the mentioned NodeJS version. This worked for me.

1

Its weird but it works for me

Go to

control panel -->System and Security--> System --> Advanced System Security--> Environment Variables

In Environment Variable popup you will edit the user variable PATH and add "C:\Windows\System32" value as semicolon separated to the existing value.

Not but not least restart the Machine.

enter image description here

0