History

Pete Bacon Darwin 321da5cc83 refactor(compiler-cli): ngcc - track non-Angular entry-points (#29643 )

Previously we completely ignored entry-points that had not been
compiled with Angular, since we do not need to compile them
with ngcc. But this makes it difficult to reason about dependencies
between entry-points that were compiled with Angular and those that
were not.

Now we do track these non-Angular compiled entry-points but they
are marked as `compiledByAngular: false`.

PR Close #29643

2019-04-29 12:37:20 -07:00

src

refactor(compiler-cli): ngcc - track non-Angular entry-points (#29643 )

2019-04-29 12:37:20 -07:00

test

refactor(compiler-cli): ngcc - track non-Angular entry-points (#29643 )

2019-04-29 12:37:20 -07:00

BUILD.bazel

refactor(ivy): move metadata registration to its own package (#29698 )

2019-04-19 11:15:25 -07:00

index.ts

feat(compiler-cli): ngcc - make logging more configurable (#29591 )

2019-04-01 11:53:28 -07:00

main-ngcc.ts

fix(ivy): ngcc - show logging via CLI by default (#29686 )

2019-04-03 15:27:39 -07:00

README.md

refactor(ivy): move ngcc into a higher level folder (#29092 )

2019-03-20 14:45:54 -04:00

README.md

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

Unit Testing

The unit tests are built and run using Bazel:

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

Integration Testing

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

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