angular-cn/packages/bazel
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
..
docs build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) 2019-02-28 12:06:36 -08:00
src feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
test test(bazel): use cross-platform file read of golden file (#31266) 2019-08-19 13:32:13 -07:00
third_party/github.com/bazelbuild/bazel/src/main/protobuf build: Add .bzl/BUILD files to @angular/bazel package (#28769) 2019-02-19 17:55:57 -08:00
BUILD.bazel refactor(bazel): Remove bazel-workspace schematics (#29148) 2019-03-07 13:04:09 -08:00
index.bzl fix(bazel): use //:tsconfig.json as the default for ng_module (#29670) 2019-04-02 15:57:11 -07:00
package.bzl build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
package.json fix(bazel): pin `@microsoft/api-extractor` (#32187) 2019-08-19 15:42:44 -07:00
protractor-utils.js build: idiomatic install of @angular/bazel npm package (#26258) (#26488) 2018-10-19 20:59:29 -07:00