History

JoostK 52544ffaa3 fix(ivy): ngcc generates setClassMetadata calls for ES5 bundles (#27438 )

ngcc would feed ngtsc with the function declaration inside of an IIFE as
that is considered the class symbol's declaration node, according to
TypeScript's `ts.Symbol.valueDeclaration`. ngtsc however only considered
variable decls and actual class decls as potential class declarations,
so given the function declaration node it would fail to generate the
`setClassMetadata` call.

ngtsc no longer makes its own assumptions about what classes look like,
but always asks the reflection host to yield this kind of information.

PR Close #27438

2018-12-17 09:35:16 -08:00

src

fix(ivy): ngcc generates setClassMetadata calls for ES5 bundles (#27438 )

2018-12-17 09:35:16 -08:00

test

fix(ivy): prevent ngcc from inadvertently dropping Ivy definitions (#27159 )

2018-12-14 15:26:15 -08: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