History

Pete Bacon Darwin 3788ebb714 fix(ivy): ngcc - don't crash if entry-points have multiple invalid dependencies (#31276 ) If an entry-point has missing dependencies then it cannot be processed and is marked as invalid. Similarly, if an entry-point has dependencies that have been marked as invalid then that entry-point too is invalid. In all these cases, ngcc should quietly ignore these entry-points and continue processing what it can. Previously, if an entry-point had more than one entry-point that was transitively invalid then ngcc was crashing rather than ignoring the entry-point. PR Close #31276		2019-06-26 08:01:43 -07:00
..
src	fix(ivy): ngcc - don't crash if entry-points have multiple invalid dependencies (#31276 )	2019-06-26 08:01:43 -07:00
test	fix(ivy): ngcc - don't crash if entry-points have multiple invalid dependencies (#31276 )	2019-06-26 08:01:43 -07:00
BUILD.bazel	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )	2019-06-25 16:25:24 -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(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )	2019-06-25 16:25:24 -07:00
main-ngcc.ts	refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )	2019-06-25 16:25:24 -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