Another process, with id #######, is currently running ngcc
AngularAngular Problem Overview
I'm trying to build and serve my project. It was working properly, I updated it from git and then suddenly when I serve it, there is an Error saying "Another process, with id 29800, is currently running ngcc." I retried "npm i", also restarted the IDE and even pc, but it still says the same.
Angular Solutions
Solution 1 - Angular
This happens when ngcc (Angular compatibility compiler) is not finished doing what it does, you must have enabled ivy
in your Angular project. read here for more info about ivy.
- First try to run
npm install
again, to see if it fixes your problem. - Try to run
ngcc
manually. - remove this file
node_modules/@angular/compiler-cli/ngcc/__ngcc_lock_file__
- If none of the above worked, then remove
node_modules
directory and trynpm i
again.
Solution 2 - Angular
The Laptop Crashed and I got this problem after restart. Removing the below file from ionic project solved the problem.
node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file
Solution 3 - Angular
Try deleting your ngcc_lock_file
in the path:
node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file
It's work for me.
Solution 4 - Angular
Fix this all in one easy command:
run npm ci
this will delete node_modules
and npm install
Solution 5 - Angular
just remove the node_modules
then run npm i
Solution 6 - Angular
I deleted the file node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file_
from the node_modules
folder and its working fine.
Solution 7 - Angular
I deleted the file node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file_ from the node_modules folder and its working fine. angular v10
Solution 8 - Angular
Just run
ionic repair
And select Yes
Solution 9 - Angular
deleting lock file in nodes module at the following location will fix this errors
*C:\Users\OneDrive\Desktop\app\node_modules\@angular\compiler-cli\ngcc\src\locking*
delete the lock-file javascript file over there.
if it still shows the same error then delete the entire lock-files folder ,restart command prompt and then it will run
Solution 10 - Angular
Also if above solutions, dosen´t work it could be that the pipeline has too little space to work with side processes. What you could do is go to angular.json and search for this object:
"budgets": [{"type": "initial","maximumWarning": "4mb","maximumError": "5mb"}]
and raise the limits on maximumError for example.
More about budgets here: angular.io/guide
Solution 11 - Angular
Had the same issue running angular with a docker file, and like suggested here I deleted ngcc_lock_file BEFORE running npm install
Solution 12 - Angular
simply run rm -rf node_modules && npm install