Hello, I am trying to build my Bazel typescript project into a docker container using the container_image rule from rules_docker. Is there any recommended solution for setting the rootDirs?
"compilerOptions": {
"rootDirs": [
".",
"../../bazel-out/host/bin/path/to",
"../../bazel-out/darwin-fastbuild/bin/path/to",
"../../bazel-out/darwin_arm64-fastbuild/bin/path/to",
"../../bazel-out/k8-fastbuild/bin/path/to",
"../../bazel-out/x64_windows-fastbuild/bin/path/to",
"../../bazel-out/darwin-dbg/bin/path/to",
"../../bazel-out/k8-dbg/bin/path/to",
"../../bazel-out/x64_windows-dbg/bin/path/to",
]
}
The issue with rules_docker is that it uses a Bazel transition which builds all of the ts_project targets in a different Bazel output dir which is suffixed with some hash that appears to change based on some factors unbeknownst to me (ie darwin_arm64-fastbuild-ST-4a519fd6d3e4), which makes it impossible to use the rootDirs workaround.
Is there any known solution to overcome this?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4