History

George Kalpakas 2954d1b5ca refactor(ivy): ngcc - only try to process the necessary properties (#32052 )

This change basically moves some checks to happen up front and ensures
we don't try to process any more properties than we absolutely need.
(The properties would not be processed before either, but we would
consider them, before finding out that they have already been processed
or that they do not exist in the entry-point's `package.json`.)

This change should make no difference in the work done by `ngcc`, but it
transforms the code in a way that makes the actual work known earlier,
thus making it easier to parallelize the processing of each property in
the future.

PR Close #32052

2019-08-08 11:14:38 -07:00

src

refactor(ivy): ngcc - only try to process the necessary properties (#32052 )

2019-08-08 11:14:38 -07:00

test

refactor(ivy): ngcc - make EntryPointJsonProperty-related types and checks a little more strict (#32052 )

2019-08-08 11:14:38 -07:00

BUILD.bazel

feat(ivy): ngcc - support ngcc "migrations" (#31544 )

2019-07-23 21:11:40 -07:00

index.ts

perf(ivy): ngcc - add a cache to the FileSystem (#30525 )

2019-07-09 09:40:46 -07:00

main-ngcc.ts

perf(ivy): ngcc - add a cache to the FileSystem (#30525 )

2019-07-09 09:40:46 -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