honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build: use vendored yarn version for bazel node toolchain (#34472) 

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 #34472
This commit is contained in:
Paul Gschwendtner 2019-12-18 17:41:24 +01:00 committed by Kara Erickson
parent 9264f43511
commit 23595272fe
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
WORKSPACE
View File

@ -40,10 +40,9 @@ node_repositories(
}, },
node_version = "10.16.0", node_version = "10.16.0",
package_json = ["//:package.json"], package_json = ["//:package.json"],
yarn_repositories = { # Label needs to explicitly specify the current workspace name because otherwise Bazel does
"1.21.1": ("yarn-v1.21.1.tar.gz", "yarn-v1.21.1", "d1d9f4a0f16f5ed484e814afeb98f39b82d4728c6c8beaafb5abc99c02db6674"), # 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_version = "1.21.1",
) )
yarn_install( yarn_install(