History

Terence D. Honles 561c0f81a0 perf(ngcc): allow immediately reporting a stale lock file (#37250 )

Currently, if an ngcc process is killed in a manner that it doesn't clean
up its lock file (or is killed too quickly) the compiler reports that it
is waiting on the PID of a process that doesn't exist, and that it will
wait up to a maximum of N seconds. This PR updates the locking code to
additionally check if the process exists, and if it does not it will
immediately bail out, and print the location of the lock file so a user
may clean it up.

PR Close #37250

2020-06-02 17:30:03 -04:00

src

perf(ngcc): allow immediately reporting a stale lock file (#37250 )

2020-06-02 17:30:03 -04:00

test

perf(ngcc): allow immediately reporting a stale lock file (#37250 )

2020-06-02 17:30:03 -04:00

BUILD.bazel

fix(ngcc): use path-mappings from tsconfig in dependency resolution (#36180 )

2020-03-24 10:16:12 -07:00

index.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -04:00

main-ivy-ngcc.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -04:00

main-ngcc.ts

build: update license headers to reference Google LLC (#37205 )

2020-05-26 14:26:58 -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