History

Pete Bacon Darwin 1df9908579 fix(ivy): ngcc - ensure generated source map paths are correct (#29556 )

Previously we were using absolute paths, but since at rendering time
we do not know exactly where the file will be written it is more correct
to  change to using relative paths. This is actually better all round
since it allows the folders to be portable to different machines, etc.

PR Close #29556

2019-03-28 15:23:35 -07:00

src

fix(ivy): ngcc - ensure generated source map paths are correct (#29556 )

2019-03-28 15:23:35 -07:00

test

fix(ivy): ngcc - ensure generated source map paths are correct (#29556 )

2019-03-28 15:23:35 -07:00

BUILD.bazel

refactor(ivy): move ngcc into a higher level folder (#29092 )

2019-03-20 14:45:54 -04:00

index.ts

refactor(ivy): ngcc - mark target entry-point as processed even if ngcc was a noop (#29092 )

2019-03-20 14:45:55 -04:00

main-ngcc.ts

refactor(ivy): ngcc - clean up the public API and export hasBeenProcessed helper (#29092 )

2019-03-20 14:45:55 -04: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