History

Pete Bacon Darwin 0c3bb6a731 fix(ivy): ngcc - capture entry-points in top-level path-mapped folders (#31027 )

The `EntryPointFinder` computes the base paths to consider
when searching for entry-points. When there are `pathMappings`
provided it works out the best top level base-paths that cover all
the potential mappings.

If this computed basePath happens to coincide with an entry-point
path itself then we were missing it.

Now we check for an entry-point even at the base-path itself.

Related to https://github.com/angular/angular-cli/pull/14755

PR Close #31027

2019-06-14 10:43:59 -07:00

src

fix(ivy): ngcc - capture entry-points in top-level path-mapped folders (#31027 )

2019-06-14 10:43:59 -07:00

test

fix(ivy): ngcc - capture entry-points in top-level path-mapped folders (#31027 )

2019-06-14 10:43:59 -07:00

BUILD.bazel

refactor(ivy): move metadata registration to its own package (#29698 )

2019-04-19 11:15:25 -07:00

index.ts

feat(ivy): ngcc - support additional paths to process (#29643 )

2019-04-29 12:37:21 -07:00

main-ngcc.ts

refactor(ivy): ngcc - remove the last remnants of path and canonical-path (#29643 )

2019-04-29 12:37:21 -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