History

Pete Bacon Darwin a827bc2e3a refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092 )

If `targetEntryPointPath` is provided to `mainNgcc` then we will now mark all
the `propertiesToConsider` for that entry-point if we determine that
it does not contain code that was compiled by Angular (for instance it has
no `...metadata.json` file).

The commit also renames `__modified_by_ngcc__` to `__processed_by_ivy_ngcc__`, since
there may be entry-points that are marked despite ngcc not actually compiling anything.

PR Close #29092

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

src

refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092 )

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

test

refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092 )

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

BUILD.bazel

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

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

index.ts

refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092 )

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

main-ngcc.ts

refactor(ivy): ngcc - clean up the public API and export hasBeenProcessed helper (#29092 )

2019-03-20 14:45:55 -04: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