History

JoostK 6b267482d7 feat(ngcc): enable migrations to apply schematics to libraries (#33362 )

When upgrading an Angular application to a new version using the Angular
CLI, built-in schematics are being run to update user code from
deprecated patterns to the new way of working. For libraries that have
been built for older versions of Angular however, such schematics have
not been executed which means that deprecated code patterns may still be
present, potentially resulting in incorrect behavior.

Some of the logic of schematics has been ported over to ngcc migrations,
which are automatically run on libraries. These migrations achieve the
same goal of the regular schematics, but operating on published library
sources instead of used code.

PR Close #33362

2019-10-25 09:16:50 -07:00

src

feat(ngcc): enable migrations to apply schematics to libraries (#33362 )

2019-10-25 09:16:50 -07:00

test

feat(ngcc): enable migrations to apply schematics to libraries (#33362 )

2019-10-25 09:16:50 -07: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): support --async flag (defaults to true) (#33192 )

2019-10-17 19:43:39 -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