History

Pete Bacon Darwin 6b39c9cf32 fix(compiler-cli): ngcc - cope with processing entry-points multiple times (#29657 )

With the new API, where you can choose to only process the first
matching format, it is possible to process an entry-point multiple
times, if you pass in a different format each time.

Previously, ngcc would always try to process the typings files for
the entry-point along with processing the first format of the current
execution of ngcc. But this meant that it would be trying to process
the typings a second time.

Now we only process the typings if they have not already been
processed as part of processing another format in another
even if it was in a different execution of ngcc.

PR Close #29657

2019-04-02 15:59:34 -07:00

src

fix(compiler-cli): ngcc - cope with processing entry-points multiple times (#29657 )

2019-04-02 15:59:34 -07:00

test

fix(compiler-cli): ngcc - cope with processing entry-points multiple times (#29657 )

2019-04-02 15:59:34 -07:00

BUILD.bazel

feat(ivy): performance trace mechanism for ngtsc (#29380 )

2019-04-01 15:13:55 -07:00

index.ts

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

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

main-ngcc.ts

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

2019-04-01 11:53:28 -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