History

Pete Bacon Darwin f8941a5b6b refactor(ngcc): change async locker timeout to 250 secs (#36838 ) Previously the `AsyncLocker` was configured to only wait 50x500ms before timing out. This is 25secs, which is often less than a normal run of ngcc, so the chance of a timeout flake was quite high. The default is now 500x500ms, which is 250secs. If this is too high for some projects then it can be changed via the `ngcc.config.js` project file. PR Close #36838		2020-05-01 09:52:10 -07:00
..
src	refactor(ngcc): change async locker timeout to 250 secs (#36838 )	2020-05-01 09:52:10 -07:00
test	feat(ngcc): allow async locking timeouts to be configured (#36838 )	2020-05-01 09:52:10 -07:00
BUILD.bazel	fix(ngcc): use path-mappings from tsconfig in dependency resolution (#36180 )	2020-03-24 10:16:12 -07: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): move `PathMappings` to separate file to avoid circular dependency (#36626 )	2020-04-29 14:28:26 -07: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): provide a unique exit code for timeouts (#36838 )	2020-05-01 09:52:09 -07: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