History

Pete Bacon Darwin 103a5b42ec fix(ivy): ngcc - resolve main property paths correctly (#31509 )

When determining if a `main` path points to a UMD or CommonJS
format, the contents of the file need to be loaded and parsed.

Previously, it was assumed that the path referred to the exact filename,
but did not account for normal module resolution semantics, where the
path may be missing an extension or refer to a directory containing an
`index.js` file.

// FW-1444

PR Close #31509

2019-07-11 11:41:11 -04:00

src

fix(ivy): ngcc - resolve main property paths correctly (#31509 )

2019-07-11 11:41:11 -04:00

test

fix(ivy): ngcc - resolve main property paths correctly (#31509 )

2019-07-11 11:41:11 -04: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

perf(ivy): ngcc - add a cache to the FileSystem (#30525 )

2019-07-09 09:40:46 -07:00

main-ngcc.ts

perf(ivy): ngcc - add a cache to the FileSystem (#30525 )

2019-07-09 09:40:46 -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