You may occasionally be unable to run npm install. You may experience problems such as commands freezing and npm displaying a “Killed” notice and breaking after a fewmile minutes..<\/p>\n\n\n\n
You can try several ways to resolve this issue as below:<\/p>\n\n\n\n
Try to npm rm -rf node_modules && npm cache clean<\/em>, then npm install again does not work too, npm still be killed.<\/p>\n\n\n\n The primary cause of this problem is unclean workspace from node modules; clearing the cache can resolve this. Yet, the issue still exists for a large number of people. Many encounter the difficulty that while the command executes flawlessly on the local machine, it also shares the same environment with the remote machine. There is only one machine configuration that differs.<\/p>\n\n\n\n Check the example of configuration:<\/strong><\/p>\n\n\n\n So, you can see that the biggest difference is memory. Here the remote machine (which is running Apache, nginx and MySQL) doesn\u2019t have enough memory for npm to build something during the installation of dependencies \u2013 many dependencies need to be rebuilt by make.<\/p>\n\n\n\n For this check your swap file in remote machine using the below command:<\/p>\n\n\n\n You will get the result as no swap file are available:<\/p>\n\n\n\n Then create a 1GB swap file (on SSD system, swap speed can be much faster)<\/p>\n\n\n\n Prepare the swap file using the below command:<\/p>\n\n\n\n And activate it by executing this command:<\/p>\n\n\n\n Continue swap file after reboot by copying configuration on to the below path:<\/p>\n\n\n\n To make swap file to be a buffer for securing the application crashes, use the below command:<\/p>\n\n\n\n Lastly, set correct permission on it:<\/p>\n\n\n\n Then, clean cache and rebuild with npm:<\/p>\n\n\n\n That\u2019s it! Install script is successfully completed. It takes just about 5 minutes for npm and make to build and install required dependencies. Then just npm start and your dashboard is online!<\/p>\n\n\n\n If you already succeed in something and fail with the same tasks, make sure to check what is different along with the software and hardware to detect the reason of failure.<\/p>\n\n\n\nSteps to Prevent npm Install From Being Killed<\/h3>\n\n\n\n
\n
sudo swapon -s<\/pre>\n\n\n\n
Filename Type Size Used Priority<\/pre>\n\n\n\n
sudo dd if=\/dev\/zero of=\/swapfile bs=1024 count=1024k<\/pre>\n\n\n\n
sudo mkswap \/swapfile<\/pre>\n\n\n\n
sudo swapon \/swapfile<\/pre>\n\n\n\n
sudo nano \/etc\/fstab<\/pre>\n\n\n\n
\/swapfile none swap sw 0 0<\/pre>\n\n\n\n
echo 10 | sudo tee \/proc\/sys\/vm\/swappiness echo vm.swappiness = 10 | sudo tee -a \/etc\/sysctl.conf<\/pre>\n\n\n\n
sudo chown root:root \/swapfile sudo chmod 0600 \/swapfile<\/pre>\n\n\n\n
npm cache clean npm install<\/pre>\n\n\n\n
Conclusion<\/h3>\n\n\n\n