Angular 9 - ngcc is already running

🐞 bug report

Description

I have an angular 9 workspace with 2 projects:

• a libary
• a showcase application for testing the library while developping it

So I’m doing a ng build my-library --prod --watch followed by npm start showcase. The first on is going right but the second one fails with

chunk {main} main.js, main.js.map (main) 2.04 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 699 bytes [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 10.6 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 341 kB [initial] [rendered] Date: 2020-02-12T08:31:44.330Z - Hash: 2061194b646fd4602d5d - Time: 2009ms

ERROR in ngcc is already running at process with id 13848. If you are running multiple builds in parallel then you should pre-process your node_modules via the command line ngcc tool before starting the builds; See https://v9.angular.io/guide/ivy#speeding-up-ngcc-compilation. (If you are sure no ngcc process is running then you should delete the lockfile at …/node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file.) ** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

🌍 Your Environment

Angular Version:

Angular CLI: 9.0.1 Node: 12.15.0 OS: win32 x64

Angular: 9.0.0 … animations, cdk, common, compiler, compiler-cli, core, forms … language-service, platform-browser, platform-browser-dynamic … router Ivy Workspace: Yes

Package Version

@angular-devkit/architect 0.900.1 @angular-devkit/build-angular 0.900.1 @angular-devkit/build-ng-packagr 0.900.1 @angular-devkit/build-optimizer 0.900.1 @angular-devkit/build-webpack 0.900.1 @angular-devkit/core 9.0.1 @angular-devkit/schematics 9.0.1 @angular/cli 9.0.1 @angular/flex-layout 9.0.0-beta.29 @ngtools/webpack 9.0.1 @schematics/angular 9.0.1 @schematics/update 0.900.1 ng-packagr 9.0.0 rxjs 6.5.4 typescript 3.7.5 webpack 4.41.2

[bolrock]

While trying to write some code like @splincode asked me, I looked more deeply to what’s happening.

I first deleted the node_modules/@angular/compiler-cli/ngcc/ngcc_lock_file

I I then noticed

• when launching ng build my-library --prod --watch the ngcc_lock_file is not created.
• when launching npm start showcase the ngcc_lock_file is created but deleted a while after.

So I supposed that the file was not correctly erased and that the ‘conflict’ is not coming from the library build watch but from a previous ng serve which did not erased the lock file.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}