History

Pete Bacon Darwin 1790b63a5d refactor(ngcc): expose the TaskDependencies mapping on BaseTaskQueue (#36083 )

Later when we implement the ability to continue processing when tasks have
failed to compile, we will also need to avoid processing tasks that depend
upon the failed task.

This refactoring exposes this list of dependent tasks in a way that can be
used to skip processing of tasks that depend upon a failed task.

It also changes the blocking model of the parallel mode of operation so
that non-typings tasks are now blocked on their corresponding typings task.
Previously the non-typings tasks could be triggered to run in parallel to
the typings task, since they do not have a hard dependency on each other,
but this made it difficult to skip task correctly if the typings task failed,
since it was possible that a non-typings task was already in flight when
the typings task failed. The result of this is a small potential degradation
of performance in async parallel processing mode, in the rare cases that
there were not enough unblocked tasks to make use of all the available
workers.

PR Close #36083

2020-03-18 15:56:21 -07:00

src

refactor(ngcc): expose the TaskDependencies mapping on BaseTaskQueue (#36083 )

2020-03-18 15:56:21 -07:00

test

refactor(ngcc): expose the TaskDependencies mapping on BaseTaskQueue (#36083 )

2020-03-18 15:56:21 -07:00

BUILD.bazel

feat(ngcc): implement source-map flattening (#35132 )

2020-02-26 12:51:35 -08:00

index.ts

refactor(ngcc): expose logging level on the logger (#35861 )

2020-03-05 18:17:15 -05:00

main-ivy-ngcc.ts

fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140 )

2019-10-14 16:29:14 +00:00

main-ngcc.ts

feat(ngcc): support invalidating the entry-point manifest (#35931 )

2020-03-11 15:01:59 -07:00

README.md

…

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