Paul Gschwendtner 9de9c8ad03 fix(bazel): protractor utils cannot start server on windows (#27915) ... * Currently the protractor utils assume that the specified Bazel server runfile can be resolved by just using the real file system. This is not the case on Windows because the runfiles are not symlinked into the working directory and need to be resolved through the runfile manifest. PR Close #27915		2019-01-07 14:49:44 -08:00
..
docs	docs(bazel): add skydoc generation (#23544)	2018-08-08 13:12:07 -07:00
src	fix(bazel): protractor utils cannot start server on windows (#27915)	2019-01-07 14:49:44 -08:00
test	fix(bazel): protractor utils cannot start server on windows (#27915)	2019-01-07 14:49:44 -08:00
BUILD.bazel	build: restrict visibility of npm_package targets (#27611)	2018-12-14 10:20:40 -08:00
check_version.js	fix(bazel): fix major/minor semver check between @angular/bazel npm packager version and angular bazel repo version (#27635)	2018-12-13 10:59:14 -08:00
index.bzl	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00
package.bzl	build: update to Bazel 0.21.0 (#27935)	2019-01-04 18:38:44 -08:00
package.json	feat: add support for typescript 3.2 (#27536)	2018-12-18 13:20:01 -08:00
protractor-utils.js	build: idiomatic install of @angular/bazel npm package (#26258) (#26488)	2018-10-19 20:59:29 -07:00
yarn.lock	fix(bazel): Read latest versions from latest-versions.ts & use semver check (#27526)	2018-12-10 16:35:42 -08:00