Skip to content

Commit

Permalink
build: use vendored yarn version for bazel node toolchain (angular#34472
Browse files Browse the repository at this point in the history
)

Instead of downloading Yarn separately for Bazel, we could use
our existing copy of Yarn that we maintain for CI jobs that do
not use Bazel. This ensures we use consistent versions of Yarn
across our CI jobs, and also avoids unnecessary downloads to the
Bazel mirror server, or Yarn download servers.

PR Close angular#34472
  • Loading branch information
devversion authored and kara committed Dec 18, 2019
1 parent 9264f43 commit 2359527
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions WORKSPACE
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,9 @@ node_repositories(
},
node_version = "10.16.0",
package_json = ["//:package.json"],
yarn_repositories = {
"1.21.1": ("yarn-v1.21.1.tar.gz", "yarn-v1.21.1", "d1d9f4a0f16f5ed484e814afeb98f39b82d4728c6c8beaafb5abc99c02db6674"),
},
yarn_version = "1.21.1",
# Label needs to explicitly specify the current workspace name because otherwise Bazel does
# not provide all needed data (like "workspace_root") to the repository context.
vendored_yarn = "@angular//:third_party/github.com/yarnpkg/yarn/releases/download/v1.21.1",
)

yarn_install(
Expand Down

0 comments on commit 2359527

Please sign in to comment.