Tried to overwrite @angular/cdk/stepper/step-header.d.ts.__ivy_ngcc_bak with an ngcc back up file, which is disallowed
Solution 1
Make sure to clean your workspace after upgrading to angular 9 and reinstall all packages/dependencies. It actually resolved most of my errors.
Cleaning workspace by deleting node_modules folder, package_lock.json and reinstalling all packages by npm install
resolved most of the issues
- Delete your
node_modules
folder - Delete
package_lock.json
- Reinstall packages after deleteing with
npm install
Solution 2
Turning enableIvy
off, did work for me.
from tsconfig
file, under angularCompilerOptions
add "enableIvy": false
Related videos on Youtube
Aniruddha Das
A self-motivated full-stack, multi-domain and solutions-orientated JavaScript, ES6, Typescript, Angular (7), AngularJS, jQuery, HTML, CSS, JAVA, J2EE, Spring, PHP, Shell Script, PL SQL, MySQL, AWS, Google App Engine, Google Datastore, JPA, Cucumber BDD Professional with more then 11+ Years of IT experience in a various IT stages including Design, developing, Unit testing and enhancement and support application.
Updated on June 04, 2022Comments
-
Aniruddha Das over 1 year
After upgrading
@angular/core
and@angular/material
usingng update
command, thengcc
command fails with below errorcommand used:
ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points
Error:
> Compiling @angular/cdk/stepper : es2015 as esm2015 > Compiling @angular/cdk/drag-drop : es2015 as esm2015 > Error: Error on worker #3: Error: Tried to overwrite node_modules/@angular/cdk/stepper/step-header.d.ts.__ivy_ngcc_bak with an ngcc back up file, which is disallowed. > at NewEntryPointFileWriter.InPlaceFileWriter.writeFileAndBackup (node_modules/@angular/compiler-cli/ngcc/src/writing/in_place_file_writer.js:37:23) > at NewEntryPointFileWriter.writeFile (node_modules/@angular/compiler-cli/ngcc/src/writing/new_entry_point_file_writer.js:64:53) > at node_modules/@angular/compiler-cli/ngcc/src/writing/new_entry_point_file_writer.js:46:69 > at Array.forEach (<anonymous>) > at NewEntryPointFileWriter.writeBundle (node_modules/@angular/compiler-cli/ngcc/src/writing/new_entry_point_file_writer.js:46:30) > at ClusterWorker.compile (node_modules/@angular/compiler-cli/ngcc/src/main.js:173:32) > at Worker.<anonymous> (node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/worker.js:44:42) > at Worker.emit (events.js:321:20) > at process.<anonymous> (internal/cluster/worker.js:32:12) > at process.emit (events.js:321:20) > at ClusterMaster.onWorkerMessage (node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:158:27) > at node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:46:95 > at ClusterMaster.<anonymous> (node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:238:57) > at step (node_modules/tslib/tslib.js:136:27) > at Object.next (node_modules/tslib/tslib.js:117:57) > at node_modules/tslib/tslib.js:110:75 > at new Promise (<anonymous>) > at Object.__awaiter (node_modules/tslib/tslib.js:106:16) > at EventEmitter.<anonymous> (node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:232:32) > at EventEmitter.emit (events.js:321:20)
-
JRA_TLL over 3 yearsRequires ng-zorro-antd v9.0.2+ acording to github.com/NG-ZORRO/ng-zorro-antd/issues/4236
-
Sanjay Achar about 3 yearsThis will compile but will render a blank page with error - Complier not found
-
Stefan Falk almost 3 yearsAh, the good old "Burn everything to the ground and continue as if nothing happened"-technique. Works (almost) every time.
-
Segev -CJ- Shmueli almost 3 yearsdeleting
node_modules
should suffice (as long as you didn't changepackage_lock.json
manually) -
Love to Code over 1 yearWorked for me too!