Paul Gschwendtner b5b3c73c8b build: allow for custom bazel binary to be used in package-builder (#43431) ... The package builder script should respect the `BAZEL` environment variable for running Bazel. If not set, it can fallback to bazelisk from the `node_modules`. Respecting this variable allows for users with a global `bazel` binary. This is desirable in some situations, like on Windows, where running Bazel inside of the Yarn environment seems slower than running a global variant. This could appear like that because projects might use different Bazel versions. In some cases, developers would want to use a single (already-warmed-up) instance of Bazel instead of launching different versions using bazelisk. (e.g. when switching a lot between repos like COMP, FW or CLI..) In any case, it doesn't hurt providing this flexibility for advanced use-cases. It's low-effort to maintain and is respected in COMP as well. PR Close #43431		2021-10-01 18:28:46 +00:00
..
angular-in-memory-web-api.js	build: update build scripts to no longer build View Engine output (#43431)	2021-10-01 18:28:42 +00:00
build-packages-dist.js	build: set executable bit for build-packages-dist script (#43431)	2021-10-01 18:28:44 +00:00
package-builder.js	build: allow for custom bazel binary to be used in package-builder (#43431)	2021-10-01 18:28:46 +00:00
zone-js-builder.js	build: make the build scripts for the various packages consistent (#41429)	2021-04-06 10:22:54 -07:00