forked from aspect-build/rules_js
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.bazelrc.common
76 lines (62 loc) · 3.65 KB
/
.bazelrc.common
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
# Bazel settings that apply to this repository.
# Take care to document any settings that you expect users to apply.
# Settings that apply only to CI are in .github/workflows/ci.bazelrc
# ======================================================================================================================
# Support for debugging Node.js tests
# Use `--config=debug` to enable these settings
# Use bazel run with `--config=debug` to turn on the NodeJS inspector agent.
# The node process will break before user code starts and wait for the debugger to connect.
# Pass the --inspect-brk option to all tests which enables the node inspector agent.
# See https://nodejs.org/de/docs/guides/debugging-getting-started/#command-line-options for more details.
run:debug -- --node_options=--inspect-brk
# Stream stdout/stderr output from each test in real-time.
# See https://docs.bazel.build/versions/master/user-manual.html#flag--test_output for more details.
test:debug --test_output=streamed
# Run one test at a time.
test:debug --test_strategy=exclusive
# Prevent long running tests from timing out.
# See https://docs.bazel.build/versions/master/user-manual.html#flag--test_timeout for more details.
test:debug --test_timeout=9999
# Always run tests even if they have cached results.
test:debug --nocache_test_results
# Changes the build output of certain rules such as terser. May not be desirable in all cases.
# Rules may change their build outputs if the compilation mode is set to dbg. For example,
# minifiers such as terser may make their output more human readable when this is set. Node.js rules that change their
# behavior based on compilation mode will pass ctx.var["COMPILATION_MODE"] to `js_binary` executables via
# the actions.run env attribute.
# See https://docs.bazel.build/versions/master/user-manual.html#flag--compilation_mode for more details.
build:debug --compilation_mode=dbg
# ======================================================================================================================
# Allow the Bazel server to check directory sources for changes.
# Recommended when using copy_directory, see
# https://github.com/aspect-build/bazel-lib/blob/main/docs/copy_directory.md
startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1
# In general, the rules in this repository assume that runfiles
# are enabled as we do not support no runfiles case.
#
# If you are developing on Windows, you must either run bazel
# with administrator priviledges or enable developer mode. If
# you do not you may hit this error on Windows:
#
# Bazel needs to create symlinks to build the runfiles tree.
# Creating symlinks on Windows requires one of the following:
# 1. Bazel is run with administrator privileges.
# 2. The system version is Windows 10 Creators Update (1703) or later
# and developer mode is enabled.
build --enable_runfiles
build --incompatible_allow_tags_propagation
# Turn off legacy external runfiles on all platforms except Windows.
# This prevents accidentally depending on this feature, which Bazel will remove.
build --nolegacy_external_runfiles
# Turn on --incompatible_strict_action_env which was on by default
# in Bazel 0.21.0 but turned off again in 0.22.0. Follow
# https://github.com/bazelbuild/bazel/issues/7026 for more details.
# This flag is needed to so that postinstall scripts can be executed
# on the host.
# See https://github.com/angular/angular/issues/27514.
build --incompatible_strict_action_env
# Enable with --config=release
build:release --stamp --workspace_status_command=$(pwd)/workspace_status.sh
# Config to enable building and testing with bzlmod
common:bzlmod --enable_bzlmod
common:bzlmod --@aspect_bazel_lib//lib:flag_bzlmod