Duarte Nunes
Duarte Nunes
That's surprising though. If I have a `ts_project` rule named "foo", using a transpiler, and a `js_library` that depends both on `foo` and on `foo_typings`, won't Bazel build the `js_library`...
This is still happening with version 4.6.0. @alexeagle, @gregmagolan any tips on how to fix this would be greatly appreciated :)
It still reproduces with 5.0.0-rc.1. I've updated the reproducer [here](https://github.com/duarten/rules_nodejs/tree/feature/repro-multiple-node-modules).
It could be! If you are on 5.x.x it may also be related to https://github.com/bazelbuild/rules_nodejs/issues/3264, so you should try to set `exports_directories_only` to `False` in your `yarn_install` or `npm_install` rule.
I think it's a bug and will be fixed in #3264, but I don't understand what exactly is causing the issue, I just had recently spent some time trying to...
@thesayyn Can you reopen this issue? #3380 doesn't fix it (this is unrelated to `exports_directories_only`). You can run the reproducer [here](https://github.com/duarten/rules_nodejs/tree/feature/repro-multiple-node-modules) to check the test is still failing.
It was intentional at some point, but it is indeed no longer necessary. Happy to close the issue unless there's something to attach to it like docs update or something.
I have an example [here](https://github.com/duarten/rust-bazel-cross) on doing cross-compilation on a macOS host to a Linux musl target. It leverages the platforms infrastructure and `--incompatible_enable_cc_toolchain_resolution`. It also uses [transitions](https://github.com/duarten/rust-bazel-cross/blob/main/build/rust-musl.bzl) to unconditionally...