History

Alan 3a7bfc721e fix(ivy): handle windows drives correctly (#30297 )

At the moment the module resolver will end up in an infinite loop in Windows because we are assuming that the root directory is always `/` however in windows this can be any drive letter example `c:/` or `d:/` etc...

With this change we also resolve the drive letter in windows, when using `AbsoluteFsPath.from` for consistence so under `/foo` will be converted to `c:/foo` this is also needed because of relative paths with different drive letters.

PR Close #30297

2019-05-13 11:26:55 -07:00

src

fix(ivy): handle windows drives correctly (#30297 )

2019-05-13 11:26:55 -07:00

test

fix(ivy): handle windows drives correctly (#30297 )

2019-05-13 11:26:55 -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