Paul Gschwendtner 1d5c44551d build: use checked-in configuration from bazel-toolchains (#31251) ... No longer uses docker in order to pull down the toolchain configs for remote build execution. We don't need to make docker a prerequisite for working on the Angular repository since we can leverage the checked-in toolchain configurations from the `@bazel-toolchains` repository. PR Close #31251		2019-06-25 10:24:43 -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	build(bazel): remove deprecated rules_nodejs NodeModuleInfo provider (#31019)	2019-06-25 10:21:07 -07:00
test	build(bazel): update //packages/bazel/test/ngc-wrapped:ngc_test test (#31019)	2019-06-25 10:21:07 -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: use checked-in configuration from bazel-toolchains (#31251)	2019-06-25 10:24:43 -07:00
package.json	fix(bazel): update peerDep ranges (#30155)	2019-04-26 12:32:35 -07:00
protractor-utils.js	build: idiomatic install of @angular/bazel npm package (#26258) (#26488)	2018-10-19 20:59:29 -07:00