History

Pete Bacon Darwin 03465b621b fix(ngcc): only lock ngcc after targeted entry-point check (#34722 ) The Angular CLI will continue to call ngcc on all possible packages, even if they have already been processed by ngcc in a postinstall script. In a parallel build environment, this was causing ngcc to complain that it was being run in more than one process at the same time. This commit moves the check for whether the targeted package has been processed outside the locked code section, since there is no issue with multiple ngcc processes from doing this check. PR Close #34722		2020-01-22 15:35:34 -08:00
..
src	fix(ngcc): only lock ngcc after targeted entry-point check (#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
README.md	refactor(ivy): move ngcc into a higher level folder (#29092 )	2019-03-20 14:45:54 -04: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

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

The unit tests are built and run using Bazel:

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

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

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