History

Alex Rickabaugh 159788685a fix(ivy): resolve resources using TS module resolution semantics (#27357 )

Previously ngtsc assumed resource files (templateUrl, styleUrls) would be
physically present in the file system relative to the .ts file which
referenced them. However, ngc previously resolved such references in the
context of ts.CompilerOptions.rootDirs. Material depends on this
functionality in its build.

This commit introduces resolution of resources by leveraging the TypeScript
module resolver, ts.resolveModuleName(). This resolver is used in a way
which will never succeed, but on failure will return a list of locations
checked. This list is then filtered to obtain the correct potential
locations of the resource.

PR Close #27357

2018-12-04 14:03:55 -08:00

src

fix(ivy): resolve resources using TS module resolution semantics (#27357 )

2018-12-04 14:03:55 -08:00

test

feat(ivy): ngcc - render private declaration exports (#26906 )

2018-11-30 14:02:03 -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