angular-cn/packages/bazel
Paul Gschwendtner b7738ef9e4 build: fix bazel protractor tests not capturing console output (#28490)
Currently we depend on the "rules_webtesting" version that is
installed by "rules_typescript//:package.bzl". This version of
the webtesting rules comes with a very old version of Chromium
and the `chromedriver` that does not support capturing console
errors properly (with stack traces). Since we have a few e2e
tests that depend on console output (e.g. playground/src/source-map),
we need to make sure that these tests can pass upon Bazel
migration.

PR Close #28490
2019-02-04 16:51:11 -05:00
..
docs docs(bazel): add skydoc generation (#23544) 2018-08-08 13:12:07 -07:00
src docs(bazel): Explain explicit version requirement (#28482) 2019-02-04 14:56:46 -05:00
test build: bump year (#27880) 2019-01-11 11:15:59 -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: fix bazel protractor tests not capturing console output (#28490) 2019-02-04 16:51:11 -05:00
package.json fix(bazel): Bazel-workspace schematics should run in ScopedTree (#28349) 2019-01-28 12:00:16 -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): Bazel-workspace schematics should run in ScopedTree (#28349) 2019-01-28 12:00:16 -08:00