How to solve npm error "npm ERR! code ELIFECYCLE"

I was issuing the npm start command with the folder of the project opened at Sublime Text. Closing ST and restarting the server did the work for me.

With cPanel on CentOS Linux (with PlanetHoster) NodeJS v10 is installed at /opt/cpanel/ea-nodejs10/bin which needs to be added to ~/.bash_profile :

PATH=$PATH:$HOME/.local/bin:$HOME/bin:/opt/cpanel/ea-nodejs10/bin 

After that I had no problem with npm install

I am using react-create-app in Windows 10, on February 2nd, 2019 with latest NodeJS 11.9.0 and npm 6.7.0 (When you install NodeJS, the npm is existing). I think case of node packages are corrupted is rarely, the main cause permission.

At the beginning, I put project directory at Desktop, it is belong to C:\ driver. I move to another directory of another driver. Therefore, I remove "file permission" concern. Every work well and simple.

cd /d D:\ mkdir temp20190202 npx create-react-app my-app cd my-app npm start 

It is ok, not put project folder in a directory of C:\ (or other driver what contains Windows Operating system).

I had the same issue with Angular 7. Just went through the following steps and error was solved.

1). Delete your node_modules folder and package-lock.json file.

2). Run npm install command.

3). Run npm audit fix command.

This had nothing to do with NPM packages for me. My Vuepress project was using a custom host name. Omitting this got things working again.

This solved me on ubuntu 16

1) Update npm and node to latest version . 2) Restart System 3) Remove node_modules and again npm i & npm start

My situation called for removing webpack folder globally, then deleting project node_modules folder, package-lock.json and running npm install, npm start

The other answers did not solve the problem for my case. This works for me:

• Try deleting your build output.
• For me, that means deleting general.dll.js

Additional Details

• Windows 10 64bit dev machine
• NPM Start running webpack generating a build file: general.dll.js
• If I get the ELIFECYCLE error upon "NPM Start" it is often after I have already successfully executed "NPM Start" but then stopped it, only to start "NPM Start" again.
• I noticed that general.dll.js showed up in some of the hard-to-understand logs

My solution:

I was missing config.env properties because I was developing on a new machine, and of course I keep my config files out of my repo.

If you are using a different machine than usual, make sure that you include any config files that are not present in the repo that gets cloned.

In my instance the following worked:

I use node version manager on account of some projects running on older versions of Node.JS

Assure the project failing is running the correct Node version.

nvm use "correct node version"

npm install and npm start should do it.

ELIFECYCLE, from what I gather, basically means you are attempting to use packages that have reach their end-of-life. Update packages worked for me.

Try completely updating the newest, stable version of both nodejs and npm:

sudo apt -y update && sudo apt -y upgrade curl -fsSL https://deb.nodesource.com/setup_16.x | sudo -E bash - sudo apt-get install -y nodejs sudo apt -y update && sudo apt -y upgrade sudo apt -y autoremove 

Then, change directories into your app directory:

cd myapp/ #Change this to match your app directory 

Remove node_modules folder

sudo rm -rf node_modules/ 

Then reinstall the packages:

npm i 

See if your app builds successfully:

npm run build 

try this commands

1- update node

curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash - 

.

sudo apt-get install -y nodejs 

2-remove node modules

 rm -rf node_modules/ package-lock.json 

3-clear cache

npm cache clear --force 

4-

npm install 

if return notice to install new version ,run it, for example

i run this command to update new version

npm install -g [email protected] 

5-

 npm run dev 

1. You have to know exactly, which is your project node version, you can check it so:

   nvm ls

Depending on whether the project is old or new, node versions will differ, causing such problems. Then you will need to upgrade or downgrade your node version. In this way:

nvm install v14.0.0 

And you have to use following version

nvm use v14.0.0 

In my case, my project's node version was 14.0.0, and my node is 16.7.0, my solution

nvm install v14.0.0 nvm use v14.0.0 npm install 

Laravel9 v9.4.0 does not support Node.js < 16.0

You should upgrade Node.js version >= 16

I am just on terminal type this line :

sudo npm link @angular/cli 

and the boom Angular CLI: 15.2.7 Node: 18.16.0 Package Manager: npm 9.5.1 OS: darwin x64

Angular: undefined ...

adding package-lock=false to my .npmrc fixed this and seems to be equivalent (superficially) to the npm rm package-lock.json && npm cache clean --force && etc. Inspo.

Here on my ubuntu 18 node 10.24.1

i need to do this:

echo "fs.inotify.max_user_watches=524288" | sudo tee -a /etc/sysctl.conf sudo sysctl -p

nmp start

or you can try to rerun "npm install" if needed.

If you get an ELIFECYCLE running inside a container, you may just need to increase the memory the container is requesting.

For instance, in a Kubernetes yaml file just add/increase the resource.request:

containers: - name: my-container image: image-example:1.4.2 resources: requests: memory: 500M # add/increase this 

And perhaps adjust resources.limits.memory too.

Well! I got this error while writing react code many times, most of the time it is because of the following two

1. When you imported something from the wrong library, for example

 import {Button} from "bootstrap"; //wrong one import {Button} from 'react-bootstrap';//the correct one 

2. When you imported two of the same name elements from different libraries

 import {Text} from 'react-native'; import {Text} from 'native-base'; 

if this is not your mistake then you should delete all node modules and install again or start a new project and work on it!.

This is an OOM issue in most cases and comes from a lack of available memory.

I managed to fix this after combining some of the recommendations here and elsewhere and I will detail them as someone may find them handy.

First of all, I will start by saying that I bought a very cheap VPS with 512 MB RAM to install Uptime Kuma and as per my review the available memory for node/npm was a little below 370 MB which was not enough to compile everything.

The VPS had no swap space so the process was getting killed due to OOM easily.

To fix this I created a 1 GB swap file and mounted it just as per the instructions here.

TL;DR, just execute these commands:

cd /var touch swap.img chmod 600 swap.img dd if=/dev/zero of=/var/swap.img bs=1024k count=1000 mkswap /var/swap.img swapon /var/swap.img echo "/var/swap.img none swap sw 0 0" >> /etc/fstab 

I did not need to do this step to prioritize swap over RAM, but you may need to so it is worth a try:

sysctl -w vm.swappiness=30 

I will not bother you with details, they are all in the article.

Next I increased the max-old-space-size to 1024 by executing:

export NODE_OPTIONS="--max-old-space-size=1024" 

As seen here. And then I ran npm successfully.

Depending on your specs and needs you may need to increase the swap file to a higher value, but it should always work to fix OOM issues.