History

Pete Bacon Darwin 50c4ec6687 fix(ivy): ngcc - resolve path-mapped modules correctly (#31450 )

Non-wild-card path-mappings were not being matched correctly.

Further path-mapped secondary entry-points that
were imported from the associated primary entry-point were not
being martched correctly.

Fixes #31274

PR Close #31450

2019-07-08 10:28:13 -07:00

src

fix(ivy): ngcc - resolve path-mapped modules correctly (#31450 )

2019-07-08 10:28:13 -07:00

test

fix(ivy): ngcc - resolve path-mapped modules correctly (#31450 )

2019-07-08 10:28:13 -07:00

BUILD.bazel

refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )

2019-06-25 16:25:24 -07:00

index.ts

refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )

2019-06-25 16:25:24 -07:00

main-ngcc.ts

refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921 )

2019-06-25 16:25:24 -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