mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
build: use bazel from node modules (#16361)
The goal of https://github.com/angular/components/commit/2ce5ffd56b70c3791331ceedeadc1f1f6daf3924 was to avoid the use of Bazel through the `node_modules` because it adds unnecessary code overhead, slows down CI and means that some tools need to be installed multiple times (such as `yarn`). Unfortunately when building a release with Bazel right now, the bazel workspace status script depends on the global `node` binary. This means that we need to bring in Node when running with the `--config=release` flag.. Since that causes inconsistent behavior and just complicates the setup, we are using Bazel through Yarn for now. Similar to how we did it for `angular/angular` with https://github.com/angular/angular/commit/8fc4ae51fb66d14f6dc82712a536c3842205fc6d.
This commit is contained in:
committed by
Jeremy Elbourn
parent
94c84edd58
commit
10370ef659
@@ -24,7 +24,7 @@ docsDistPath="${projectPath}/dist/docs"
|
||||
docsContentPath="${projectPath}/tmp/material2-docs-content"
|
||||
|
||||
# Path to the release output of the Bazel "@angular/material-examples" NPM package.
|
||||
examplesPackagePath="$(bazel info bazel-bin)/src/material-examples/npm_package"
|
||||
examplesPackagePath="$(yarn -s bazel info bazel-bin)/src/material-examples/npm_package"
|
||||
|
||||
# Git clone URL for the material2-docs-content repository.
|
||||
docsContentRepoUrl="https://github.com/angular/material2-docs-content"
|
||||
|
||||
Reference in New Issue
Block a user