Alex Eagle

@devversion any chance you have time to get this angular example upgrade working so we can use TS 4.4?

I think it's essentially fixed by #3191 since `@bazel/typescript` has the wider peer dep. The rest of this change is still stuck :(

no, there are two Bazel modules in this repo: `rules_nodejs` which is on bazel-central-registry and `build_bazel_rules_nodejs` which isn't. I don't plan to spend any time on the latter, since all...

All the maintainers are now working on aspect rules_js so yes, over the course of the next months as it matures past 1.0 I'd recommend users migrate. It's a rewrite...

I noticed from the example above that https://github.com/yarnpkg/berry/archive/refs/tags/@yarnpkg/cli/3.1.0.tar.gz is over 150MB file so I don't think that's quite the right workaround either.

Re-opening this issue to get the yarn_versions builtin to support more versions.

I checked out that pr again, and commented there. It doesn't actually work, and I don't have a client who needs it. Contributions welcome of course 😁

Just to wrap this up, rules_nodejs is no longer maintained and rules_js standardized on pnpm because it's lockfile allows us to port the node_modules layout to starlark, which allows lazy...

I think it's quite reasonable for us to publish releases to github which consist of the existing .tgz as well as a distribution of the puller binary for each platform....

My impression is that this is PR unlikely to proceed, because the right answer is to stop having custom binaries at all. There are plenty of tools in the ecosystem...