History

Pete Bacon Darwin a581773887 perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525 )

Previously, ngcc had to walk the entire `node_modules` tree looking for
entry-points, even if it only needed to process a single target entry-point
and its dependencies.

This added up to a few seconds to each execution of ngcc, which is noticeable
when being run via the CLI integration.

Now, if an entry-point target is provided, only that target and its entry-points
are considered rather than the whole folder tree.

PR Close #30525

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

src

perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525 )

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

test

perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525 )

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

BUILD.bazel

refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )

2019-06-25 16:25:24 -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