Alex Eagle

That's not how it works though. It depends what outputs you request from the js_library. If it always propagates declarationinfo into runfiles then it causes the eager type checking which...

Not necessarily. It depends which providers that dependency on the js_library asks for. You have to consider how the action graph is finer-grained and different shape, and is "lowered" into...

Will users run into a problem with passing uncompiled requirements to pip_parse? Do you get an error if your requirements.txt just contains "pep8" or something?

Cool, @groodt we should make sure the next release includes a breaking change section in the release notes as well to make this discoverable

> not a standard tool in Bazel-based workflows. This is true for languages where a robust Gazelle plugin isn't available yet. However in Go, where it works best, every single...

https://github.com/bazelbuild/rules_nodejs/wiki/Debugging-problems-with-ts_project is my usual procedure for figuring these out. Adding `--traceResolution` to the //app/subapp:lib and running `bazel build //app/subapp:lib` shows `tsc` says ``` ======== Module name '../num' was successfully resolved...

Let's keep it open until we're sure the workaround is stable. Based on https://github.com/bazelbuild/bazel/pull/14251/files I think @fmeum is our expert here - Fabian do you have an estimate of how...

@abrmv that hash should be stable, as @fmeum says it's > a truncated SHA256 hash of all build settings that have been changed by transitions at some point on the...

Looks same or adjacent to bugs @gregmagolan is planning to track down soon

@aranguyen the commit in rules_nodejs didn't actually enable the flag https://github.com/bazelbuild/rules_nodejs/pull/2536/files#diff-544556920c45b42cbfe40159b082ce8af6bd929e492d076769226265f215832fR56 I'll try again now...