History

Pete Bacon Darwin a107e9edc6 feat(ngcc): lock ngcc when processing (#34722 )

Previously, it was possible for multiple instance of ngcc to be running
at the same time, but this is not supported and can cause confusing and
flakey errors at build time.

Now, only one instance of ngcc can run at a time. If a second instance
tries to execute it fails with an appropriate error message.

See https://github.com/angular/angular/issues/32431#issuecomment-571825781

PR Close #34722

2020-01-22 15:35:34 -08:00

src

feat(ngcc): lock ngcc when processing (#34722 )

2020-01-22 15:35:34 -08:00

test

feat(ngcc): lock ngcc when processing (#34722 )

2020-01-22 15:35:34 -08:00

BUILD.bazel

perf(ivy): reuse prior analysis work during incremental builds (#34288 )

2019-12-12 13:11:45 -08:00

index.ts

refactor(ngcc): add support for asynchronous execution (#32427 )

2019-09-09 15:55:13 -04:00

main-ivy-ngcc.ts

fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140 )

2019-10-14 16:29:14 +00:00

main-ngcc.ts

fix(ngcc): render legacy i18n message ids by default (#34135 )

2019-12-03 10:15:53 -08:00

README.md

refactor(ivy): move ngcc into a higher level folder (#29092 )

2019-03-20 14:45:54 -04:00

README.md

Angular Compatibility Compiler (ngcc)

This compiler will convert node_modules compiled with ngc, into node_modules which appear to have been compiled with ngtsc.

This conversion will allow such "legacy" packages to be used by the Ivy rendering engine.

Building

The project is built using Bazel:

yarn bazel build //packages/compiler-cli/ngcc

Unit Testing

The unit tests are built and run using Bazel:

yarn bazel test //packages/compiler-cli/ngcc/test

Integration Testing

There are tests that check the behavior of the overall executable:

yarn bazel test //packages/compiler-cli/ngcc/test:integration