Alex Eagle 026b7e34b3 build: update yarn version (#27193) ... Some engineers were already on Yarn 0.10.x which was permitted by the range in our package.json#engines However this introduced 'integrity sha512' lines into the yarn.lock files. Then when engineers use yarn 0.9 (in particular, Bazel did this) then the lock files get tons of meaningless edits. We could force everyone back to yarn 0.9 but this commit chooses to instead advance everyone past 0.10 PR Close #27193		2018-11-21 07:46:22 -08:00
..
src	build: update to latest Bazel rules_typescript (#27138)	2018-11-17 12:19:32 -08: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: update yarn version (#27193)	2018-11-21 07:46:22 -08: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