History

George Kalpakas 1a34fbce25 fix(ngcc): rename the executable from ivy-ngcc to ngcc (#33140 )

Previously, the executable for the Angular Compatibility Compiler
(`ngcc`) was called `ivy-ngcc`. This would be confusing for users not
familiar with our internal terminology, especially given that we call it
`ngcc` in all our docs and presentations.

This commit renames the executable to `ngcc` and replaces `ivy-ngcc`
with a script that errors with an informative message (prompting the
user to use `ngcc` instead).

Jira issue: [FW-1624](https://angular-team.atlassian.net/browse/FW-1624)

PR Close #33140

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

src

refactor(core): rename ngDirectiveDef to ɵdir (#33110 )

2019-10-14 16:20:11 +00:00

test

refactor(core): rename ngDirectiveDef to ɵdir (#33110 )

2019-10-14 16:20:11 +00:00

BUILD.bazel

feat(ngcc): support version ranges in project/default configurations (#33008 )

2019-10-10 13:59:57 -07:00

index.ts

refactor(ngcc): add support for asynchronous execution (#32427 )

2019-09-09 15:55:13 -04: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): expose --create-ivy-entry-points option on ivy-ngcc (#33049 )

2019-10-09 13:16:16 -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