Skip to content

Commit cd1e62a

Browse files
committed
build: enable runfiles on windows
This is necessary for Windows and `rules_js`, avoiding errors like: FATAL: aspect_rules_js[js_binary]: the entry_point '/c/Users/pgschwendtner/_bazel_google/pgschwendtner/arkyigd2/execroot/_main/bazel-out/x64_windows-fastbuild/bin/external/npm_typescript/ts_project_options_validator.js' not found
1 parent dbc07a1 commit cd1e62a

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

.bazelrc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,12 @@ build --nolegacy_external_runfiles
1515
run --nolegacy_external_runfiles
1616
test --nolegacy_external_runfiles
1717

18+
# Enable runfiles even on Windows.
19+
# This is necessary for `rules_js`. A little technical example for future history:
20+
# A `js_binary` may execute in the `exec` build transition, and the runfiles of that
21+
# binary would be in the transitioned `bazel-out`, and not `BIN_DIR` as set via Starlark.
22+
build --enable_runfiles
23+
1824
# The nested Bazel integration test workspace should not be analysed as part of
1925
# Skyframe, but should also not be ignored in order to be able to glob for its files.
2026
# TODO: Simplify this once https://github.com/bazelbuild/bazel/issues/12034 is fixed

0 commit comments

Comments
 (0)