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
..
src	build: update to rules_nodejs 0.32.2 (#31325)	2019-07-01 14:16:42 -07:00
test/e2e	build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824)	2019-07-26 15:01:25 -07:00
.bazelignore	build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627)	2019-06-11 00:03:11 +00:00
.bazelrc	build(bazel): add build --incompatible_list_based_execution_strategy_selection=false flag (#31325)	2019-07-01 14:16:42 -07:00
BUILD.bazel	test: bazel integration test should use angular npm packages (#28762)	2019-02-19 12:53:19 -08:00
WORKSPACE	build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824)	2019-07-26 15:01:25 -07:00
angular-metadata.tsconfig.json	feat: make the Ivy compiler the default for ngc (#32219)	2019-08-20 16:41:08 -07:00
package.json	build(zone.js): update zone.js to 0.10.2 (#31975)	2019-08-16 09:56:41 -07:00
protractor.conf.js	feat(bazel): protractor_web_test_suite for release (#24787)	2018-07-12 16:34:45 -04:00
yarn.lock	build(zone.js): update zone.js to 0.10.2 (#31975)	2019-08-16 09:56:41 -07:00