History

Pete Bacon Darwin 933cbfb828 fix(ngcc): force ngcc to exit on error (#36622 )

For some reason (possibly related to async/await promises)
the ngcc process is not exiting when spawned from the CLI
when there has been an error (such as when it timesout waiting
for a lockfile to become free).

Calling `process.exit()` directly fixes this.

Fixes #36616

PR Close #36622

2020-04-15 09:24:54 -07:00

src

fix(ngcc): correctly detect external files from nested node_modules/ (#36559 )

2020-04-10 09:10:26 -07:00

test

fix(ngcc): correctly detect external files from nested node_modules/ (#36559 )

2020-04-10 09:10:26 -07:00

BUILD.bazel

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

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

index.ts

style(ngcc): reformat of ngcc after clang update (#36447 )

2020-04-06 09:26:58 -07: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

fix(ngcc): force ngcc to exit on error (#36622 )

2020-04-15 09:24:54 -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