History

Pete Bacon Darwin 55ea8da6eb refactor(ivy): ngcc - clean up the public API and export hasBeenProcessed helper (#29092 )

Now the public API does not contain internal types, such as `AbsoluteFsPath` and
`EntryPointJsonProperty`. Instead we just accept strings and then guard them in
`mainNgcc` as appropriate.

A new public API function (`hasBeenProcessed`) has been exported to allow programmatic
checking of the build marker when the package.json contents are already known.

PR Close #29092

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

src

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

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

test

refactor(ivy): ngcc - clean up the public API and export hasBeenProcessed helper (#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 - clean up the public API and export hasBeenProcessed helper (#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