angular-cn/packages/compiler-cli/integrationtest/third_party_src
Alex Rickabaugh ec4381dd40 feat: make the Ivy compiler the default for ngc (#32219)
This commit switches the default value of the enableIvy flag to true.
Applications that run ngc will now by default receive an Ivy build!

This does not affect the way Bazel builds in the Angular repo work, since
those are still switched based on the value of the --define=compile flag.
Additionally, projects using @angular/bazel still use View Engine builds
by default.

Since most of the Angular repo tests are still written against View Engine
(particularly because we still publish VE packages to NPM), this switch
also requires lots of `enableIvy: false` flags in tsconfigs throughout the
repo.

Congrats to the team for reaching this milestone!

PR Close #32219
2019-08-20 16:41:08 -07:00
..
README.md refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
comp.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
directive.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
module.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
other_comp.ts feat(compiler): add source files to xmb/xliff translations (#14705) 2017-04-14 09:06:25 -07:00
other_module.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
tsconfig-build.json feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00

README.md

This folder emulates consuming precompiled modules and components. It is compiled separately from the other sources under src to only generate *.js / *.d.ts / *.metadata.json files, but no *.ngfactory.ts files.

** WARNING ** Do not import components/directives from here directly as we want to test that ngc still compiles them when they are not imported.