History

Pete Bacon Darwin 38ad1d97ab fix(ngcc): handle entry-points within container folders (#36305 ) The previous optimizations in #35756 to the `DirectoryWalkerEntryPointFinder` were over zealous with regard to packages that have entry-points stored in "container" directories in the package, where the container directory was not an entry-point itself. Now we will also walk such "container" folders as long as they do not contain `.js` files, which we regard as an indicator that the directory will not contain entry-points. Fixes #36216 PR Close #36305		2020-04-01 13:20:52 -07:00
..
src	fix(ngcc): handle entry-points within container folders (#36305 )	2020-04-01 13:20:52 -07:00
test	fix(ngcc): handle entry-points within container folders (#36305 )	2020-04-01 13:20:52 -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): expose logging level on the logger (#35861 )	2020-03-05 18:17:15 -05: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): use path-mappings from tsconfig in dependency resolution (#36180 )	2020-03-24 10:16:12 -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