honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/compiler-cli/ngcc
History
Pete Bacon Darwin 083fb99033 fix(ivy): ngcc - fail build-marker check if any formats were compiled with different ngcc (#29092) 
Now we check the build-marker version for all the formats
rather than just the one we are going to compile.

This way we don't get into the situation where one format was
built with one version of ngcc and another format was built with
another version.

PR Close #29092
 		2019-03-20 14:45:55 -04:00
..
src fix(ivy): ngcc - fail build-marker check if any formats were compiled with different ngcc (#29092) 2019-03-20 14:45:55 -04:00
test fix(ivy): ngcc - fail build-marker check if any formats were compiled with different ngcc (#29092) 2019-03-20 14:45:55 -04:00
BUILD.bazel refactor(ivy): move ngcc into a higher level folder (#29092) 2019-03-20 14:45:54 -04:00
README.md refactor(ivy): move ngcc into a higher level folder (#29092) 2019-03-20 14:45:54 -04:00
index.ts refactor(ivy): ngcc - clean up the public API and export `hasBeenProcessed` helper (#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

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