History

Pete Bacon Darwin c016066d9b fix(ivy): ngcc should not break lifecycle hooks (#26856 )

Previously the ivy definition calls we going directly after the
class constructor function But this meant that the lifecycle
hooks attached to the prototype were ignored by the ngtsc
compiler.

Now the definitions are written to the end of the IIFE block,
just before the return statement.

Closes #26849

PR Close #26856

2018-11-02 10:38:08 -07:00

src

fix(ivy): ngcc should not break lifecycle hooks (#26856 )

2018-11-02 10:38:08 -07:00

test

fix(ivy): ngcc should not break lifecycle hooks (#26856 )

2018-11-02 10:38:08 -07:00

BUILD.bazel

build: update canonical-path dependency (#26719 )

2018-11-01 13:49:10 -07:00

index.ts

feat(ivy): ngcc project skeleton (#24897 )

2018-07-27 17:15:31 -07:00

main-ngcc.ts

feat(ivy): ngcc project skeleton (#24897 )

2018-07-27 17:15:31 -07:00

README.md

build: use bazel version from node modules (#26691 )

2018-10-30 16:19:13 -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/src/ngcc

Unit Testing

The unit tests are built and run using Bazel:

yarn bazel test //packages/compiler-cli/src/ngcc/test

Integration Testing

There are tests that check the behaviour of the overall executable:

yarn bazel test //packages/compiler-cli/test/ngcc