Alex Eagle

Many ruleset users wrap the upstream rules with a macro that sets defaults, enforces policies, or creates an additional rule. Gazelle can generate rules with a `load` statement that ensures...

Turn on incompatible_python_disallow_native_rules for end-to-end tests

2

I'd like to enable that option in a repo downstream of rules_python, but it seems like there's a violation shipped with the project: ``` ERROR: /private/var/tmp/_bazel_alexeagle/3eecd93732ac7c6f4f360a54a468da50/external/rules_python~0.27.1~python~python_3_9_aarch64-apple-darwin/BUILD.bazel:63:11: in py_runtime rule @@rules_python~0.27.1~python~python_3_9_aarch64-apple-darwin//:py3_runtime:...

Ship a 1.0 release

3

This is the semver way to signal to our users that the code is stable and they can rely on us to have a responsible release cadence and not break...

Consolidate logic for collecting js inputs from providers

3

in https://github.com/bazelbuild/rules_nodejs/commit/5ad15960e69906a2c3e2484be9b17d1a77f83221 we observed that this logic is inconsistent. We should have a starlark helper function to iterate through the providers on the `deps` and collect the exposed JS files...

In rules_nodejs core, we should provide the primitives for building a variety of nodejs/browser toolchains. We can't pick all the winners. One example is `ts_project` where we made some decisions....

stop putting node_modules in runfiles

4

I've been trying to make Bazel faster on my slow Mac at home, where runfiles creation takes minutes for real-sized projects. But lots of things are broken. For example, in...