Paul Gschwendtner 8fc4ae51fb build: use bazel version from node modules (#26691) ... * No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally. * This also reduces the amount of packages that need to be published (ngcontainer is removed) PR Close #26691		2018-10-30 16:19:13 -04:00
..
src	build: review comments addressed (#26488)	2018-10-19 20:59:29 -07:00
test/e2e	build: idiomatic install of @angular/bazel npm package (#26258) (#26488)	2018-10-19 20:59:29 -07:00
.bazelrc	build: idiomatic install of @angular/bazel npm package (#26258) (#26488)	2018-10-19 20:59:29 -07:00
BUILD.bazel	build(bazel): use fine-grained npm deps (#26111) (#26488)	2018-10-19 20:59:29 -07:00
WORKSPACE	build: review comments addressed (#26488)	2018-10-19 20:59:29 -07:00
package.json	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00
protractor.conf.js	feat(bazel): protractor_web_test_suite for release (#24787)	2018-07-12 16:34:45 -04:00
yarn.lock	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00