History

Pete Bacon Darwin c59717571e fix(ivy): ngcc - handle missing entry-point dependencies better (#30270 ) If an entry-point has a missing dependency then all the entry-points that would have pointed to that dependency are also removed from the dependency graph. Previously we were still processing the dependencies of an entry-point even if it had already been removed from the graph because it depended upon a missing dependency that had previously been removed due to another entry-point depending upon it. This caused the dependency processing to crash rather than gracefully logging and handling the missing invalid entry-point. Fixes #29624 PR Close #30270		2019-05-07 10:24:48 -07:00
..
src	fix(ivy): ngcc - handle missing entry-point dependencies better (#30270 )	2019-05-07 10:24:48 -07:00
test	fix(ivy): ngcc - handle missing entry-point dependencies better (#30270 )	2019-05-07 10:24:48 -07:00
BUILD.bazel	refactor(ivy): move metadata registration to its own package (#29698 )	2019-04-19 11:15:25 -07:00
README.md	refactor(ivy): move ngcc into a higher level folder (#29092 )	2019-03-20 14:45:54 -04:00
index.ts	feat(ivy): ngcc - support additional paths to process (#29643 )	2019-04-29 12:37:21 -07:00
main-ngcc.ts	refactor(ivy): ngcc - remove the last remnants of `path` and `canonical-path` (#29643 )	2019-04-29 12:37:21 -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