.bazelrc - third_party/github/bazel-contrib/rules_nodejs - Git at Google

 # TODO: migrate all root WORKSPACE dependencies to MODULE.bazel
 # https://github.com/bazel-contrib/rules_nodejs/issues/3695
 common --noenable_bzlmod
 common --enable_workspace

 # 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).
 common --test_output=errors

 # 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 `yarn bazel`.
 # See https://github.com/angular/angular/issues/27514.
 common --incompatible_strict_action_env

 # Turn off legacy external runfiles
 # This prevents accidentally depending on this feature, which Bazel will remove.
 common --nolegacy_external_runfiles

 # Don’t want to push a rules author to update their deps if not needed.
 # https://bazel.build/reference/command-line-reference#flag--check_direct_dependencies
 # https://bazelbuild.slack.com/archives/C014RARENH0/p1691158021917459?thread_ts=1691156601.420349&cid=C014RARENH0
 common --check_direct_dependencies=off

 # In the root MODULE.bazel file we don't set include_headers on the nodejs toolchain
 # so the `//nodejs/headers:current_node_cc_headers`` target will not build. This target
 # is instead tested in `e2e/headers``
 common --deleted_packages=nodejs/headers

 # 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
	# TODO: migrate all root WORKSPACE dependencies to MODULE.bazel
	# https://github.com/bazel-contrib/rules_nodejs/issues/3695
	common --noenable_bzlmod
	common --enable_workspace

	# 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).
	common --test_output=errors

	# 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 `yarn bazel`.
	# See https://github.com/angular/angular/issues/27514.
	common --incompatible_strict_action_env

	# Turn off legacy external runfiles
	# This prevents accidentally depending on this feature, which Bazel will remove.
	common --nolegacy_external_runfiles

	# Don’t want to push a rules author to update their deps if not needed.
	# https://bazel.build/reference/command-line-reference#flag--check_direct_dependencies
	# https://bazelbuild.slack.com/archives/C014RARENH0/p1691158021917459?thread_ts=1691156601.420349&cid=C014RARENH0
	common --check_direct_dependencies=off

	# In the root MODULE.bazel file we don't set include_headers on the nodejs toolchain
	# so the `//nodejs/headers:current_node_cc_headers`` target will not build. This target
	# is instead tested in `e2e/headers``
	common --deleted_packages=nodejs/headers

	# 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