Hello, i'm trying to run multiple angular builds in parallel in a yarn workspaces project. To do so I am preproccessing the node_modules folder by running ngcc manually beforehand. Unfortunately this doesn't seem to work and ng build is still running ngcc thus acquiring a lock on node_modules and preventing my parallel build. Any advice? (Thank you)
#Angular build in parallel + yarn workspaces
modest shadow
...
Another process, with id 93405, is currently running ngcc.
Waiting up to 250s for it to finish.
(If you are sure no ngcc process is running then you should delete the lock-file at /home/santosp/Github/work/Modular-Teepee/node_modules/.ngcc_lock_file.)
...
I wonder if I can disable ngcc from running all together since I run it manually?
modest shadow
I realise this is a very niche question but if anyone has any thoughts shoot them, please
modest shadow
🙏
modest shadow
Update: Running ngcc beforehand seems to work since when ngcc triggers in ng build it won't have the lock for longer than a few seconds (and it ships with a default 250s retry). You get really annoying output messages but hey its better than nothing. I'm working to simply modify ngcc itself temporarily so it doesn't after the preprocess step or simply prevent it from writing locks to node_modules