Alex Eagle

Fabian recommends https://github.com/sgammon/rules_graalvm as an alternative, so we could ship a pre-compiled subprocess that doesn't leak so many dependencies.

A bunch of requests for help with Playwright recently, which would be another case for this

@stevenpollack I think it would be great, but it's a matter of maintainer resources. A few other companies have made donations to https://opencollective.com/aspect-build/projects/rules_js but there's no budget there now. Does...

@MorganR we're strongly considering donating the implementation from aspect-cli to this repo. Would you like to discuss joining efforts? Maybe on Bazel slack?

Hm, remembering what I did here... https://github.com/aspect-build/rules_py/commit/f2240acff1976373b6da86be2e9d962f926bade9#diff-6878df526d6e39f46c6e953f0cfcc2e5b7938d5c4d2cbec0657e78c99b931239R80-R81 "While marked label, it is more treated as a string" I suspect this is a breaking change, in some cases users might already...

The top-level workflow is just https://pnpm.io/cli/patch - but we should document this, and I think there's also a bit where rules_js needs to know about the patch files that maybe...

Possible that Aspect CLI could have `patch` command, which would apply to bazel modules as well (https://github.com/aspect-build/silo/issues/828 for Aspect ppl who can see that repo)

I pinged on https://github.com/grpc/grpc-web/pull/1456#issuecomment-2664173051 to get a release with the fixes

+1 - there's not enough info in the original post for us to debug this. > How to reproduce > No response

I'd be opposed to this idea simply because Bazel claims to provide reproducible builds, and without pinning/locking requirements you could get different transitive dependencies when you rebuild at the same...