angular-docs-cn/integration/bazel
George Kalpakas 4ece0eb27c build: use exact versions for integration project dependencies (#33968)
Since we cannot run `yarn install` with the `--frozen-lockfile` option
(because we want to be able to install the locally built Angular
packages), integration project lockfiles are susceptible to getting
out-of-sync with the corresponding `package.json`. When this happens,
yarn will install the latest available version that satisfies the
version range specified in `package.json`.

This commit adds another line of defense, by specifying exact versions
for the dependencies in `package.json` files (i.e. `1.33.7` instead of
`^1.33.0`). While transitive dependencies will be unpinned, this still
ensures that the same version of direct dependencies will be installed
in case of an out-of-sync lockfile, thus reducing the probability of
random failures.

PR Close #33968
2019-11-26 16:08:32 -08:00
..
src fix(bazel): ng_module should not emit shim files under bazel and Ivy (#33765) 2019-11-22 16:52:08 -05:00
test/e2e build: update to nodejs rules 0.37.1 (#32151) 2019-09-25 11:29:12 -07:00
.bazelignore build(bazel): update to nodejs rules 0.30.1 & bazel 0.26.0 (#30627) 2019-06-11 00:03:11 +00:00
.bazelrc build: remove remaining internal references to define=compile flag (#33983) 2019-11-26 16:38:40 -05:00
BUILD.bazel test: bazel integration test should use angular npm packages (#28762) 2019-02-19 12:53:19 -08:00
WORKSPACE build: update to rules_nodejs 0.40.0 (#33802) 2019-11-13 13:33:38 -08:00
package.json build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00
protractor.conf.js
yarn.lock build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00