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
..
symbol_extractor_spec	test(ivy): symbol extractor should handle different compile options (#24677)	2018-06-28 17:51:42 -04:00
BUILD.bazel	build(bazel): use fine-grained npm deps (#26111) (#26488)	2018-10-19 20:59:29 -07:00
cli.ts	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00
index.bzl	build: fix symbol-extractor by passing through "compile" as environmental variable (#26735)	2018-10-26 14:48:05 -04:00
symbol_extractor.ts	style: tslint enforces no debugger statements left behind (#25532)	2018-08-16 16:00:22 -07:00
symbol_extractor_spec.ts	test: Add bundle symbol extractor tool (#22002)	2018-02-13 11:28:54 -08:00