0% found this document useful (0 votes)
159 views2 pages

Bazelrc

This document contains Bazel configuration settings for JavaScript and Node.js workspaces. It sets options like caching build outputs, specifying test output formats, enabling debugging for Node.js tests, and defining environment variables for rules. It also loads any user-specific settings from a .bazelrc.user file.

Uploaded by

sharelock4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
159 views2 pages

Bazelrc

This document contains Bazel configuration settings for JavaScript and Node.js workspaces. It sets options like caching build outputs, specifying test output formats, enabling debugging for Node.js tests, and defining environment variables for rules. It also loads any user-specific settings from a .bazelrc.user file.

Uploaded by

sharelock4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

# Common Bazel settings for JavaScript/NodeJS workspaces

# This rc file is automatically discovered when Bazel is run in this workspace,


# see https://docs.bazel.build/versions/master/guide.html#bazelrc
#
# The full list of Bazel options: https://docs.bazel.build/versions/master/command-
line-reference.html

# Cache action outputs on disk so they persist across output_base and bazel
shutdown (eg. changing branches)
build --disk_cache=.cache/bazel-disk-cache

# Use remote cache by adding the following to .bazelrc.user


# build --remote_http_cache=https://storage.googleapis.com/geo-devrel-bazel-cache
--google_default_credentials

# Specifies desired output mode for running tests.


# Valid values are
# 'summary' to output only test status summary
# 'errors' to also print test logs for failed tests
# 'all' to print logs for all tests
# 'streamed' to output logs for all tests in real time
# (this will force tests to be executed locally one at a time regardless of
--test_strategy value).
test --test_output=errors

# Support for debugging NodeJS tests


# Add the Bazel option `--config=debug` to enable this
# --test_output=streamed
# 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_strategy=exclusive
# Run one test at a time.
# --test_timeout=9999
# Prevent long running tests from timing out
# See https://docs.bazel.build/versions/master/user-manual.html#flag--
test_timeout for more details.
# --nocache_test_results
# Always run tests
# --node_options=--inspect-brk
# 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.
# --define=VERBOSE_LOGS=1
# Rules will output verbose logs if the VERBOSE_LOGS environment variable is
set. `VERBOSE_LOGS` will be passed to
# `nodejs_binary` and `nodejs_test` via the default value of the
`default_env_vars` attribute of those rules.
# --compilation_mode=dbg
# Rules may change their build outputs if the compilation mode is set to dbg.
For example,
# mininfiers such as terser may make their output more human readable when this
is set. `COMPILATION_MODE` will be passed to
# `nodejs_binary` and `nodejs_test` via the default value of the
`default_env_vars` attribute of those rules.
# See https://docs.bazel.build/versions/master/user-manual.html#flag--
compilation_mode for more details.
test:debug --test_output=streamed --test_strategy=exclusive --test_timeout=9999
--define=VERBOSE_LOGS=1
# 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.
run:debug --define=VERBOSE_LOGS=1 -- --node_options=--inspect-brk
# The following option will change the build output of certain rules such as terser
and may not be desirable in all cases
build:debug --compilation_mode=dbg

# Turn off legacy external runfiles


# 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 the bazel cache is not invalidated
# when running bazel via `npm bazel`.
# See https://github.com/angular/angular/issues/27514.
build --incompatible_strict_action_env
run --incompatible_strict_action_env

# for sandboxes outside of google domains


https://console.cloud.google.com/apis/credentials/key/6494fc42-0d1e-4bab-a236-
59669ad39214?project=maps-sandbox-api-keys
build --action_env
GOOGLE_MAPS_JS_SAMPLES_SANDBOX_KEY=AIzaSyDcwGyRxRbcNGWOFQVT87A1mkxEOfm8t0w
run --action_env
GOOGLE_MAPS_JS_SAMPLES_SANDBOX_KEY=AIzaSyDcwGyRxRbcNGWOFQVT87A1mkxEOfm8t0w

build --action_env
GOOGLE_MAPS_JS_SAMPLES_KEY=AIzaSyB41DRUbKWJHPxaFjMAwdrzWzbVKartNGg # low quota
restricted key
run --action_env GOOGLE_MAPS_JS_SAMPLES_KEY=AIzaSyB41DRUbKWJHPxaFjMAwdrzWzbVKartNGg
# User should provide own key to run

build --worker_sandboxing

# Load any settings specific to the current user.


# .bazelrc.user should appear in .gitignore so that settings are not shared with
team members
# This needs to be last statement in this
# config, as the user configuration should be able to overwrite flags from this
file.
# See https://docs.bazel.build/versions/master/best-practices.html#bazelrc
# (Note that we use .bazelrc.user so the file appears next to .bazelrc in directory
listing,
# rather than user.bazelrc as suggested in the Bazel docs)
try-import %workspace%/.bazelrc.user

You might also like