v3.3.1

Many companies are successfully building with rules_js.
If you're getting value from the project, please let us know!
Just comment on our Adoption Discussion.

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_js", version = "3.3.1")

# Translate the pnpm-lock.yaml file to bazel targets
npm = use_extension("@aspect_rules_js//npm:extensions.bzl", "npm")
npm.npm_translate_lock(
    name = "npm",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)
use_repo(npm, "npm")

# Allows developers to use the matching pnpm version, for example:
# bazel run -- @pnpm --dir /home/runner/work/rules_js/rules_js install
pnpm = use_extension("@aspect_rules_js//npm:extensions.bzl", "pnpm", dev_dependency = True)
use_repo(pnpm, "pnpm")

By default you get the node version from DEFAULT_NODE_VERSION in @rules_nodejs//nodejs:repositories.bzl
Optionally you can pin a different version using rules_nodejs:

bazel_dep(name = "rules_nodejs", version = "6.7.3")
node = use_extension("@rules_nodejs//nodejs:extensions.bzl", "node")
node.toolchain(node_version = "24.13.0")

What's Changed

• fix(coverage): sh toolchain is optional for the merger by @jbedard in #2950
• ci: do not let a cached test result stand in for a coverage run by @jbedard in #2951
• refactor: build the coverage test rules from one factory by @jbedard in #2952
• test: e2e coverage workspace covering the supported scenarios by @jbedard in #2953
• test: assert coverage merger behavior in bash, not appended JS by @jbedard in #2954
• revert: feat: use bazel-lib run_binary's native stdout/stderr/exit_co… by @acozzette in #2955
• fix(coverage): generate lcov report in the test action by @jbedard in #2932
• refactor: directly run node from shell using exec when not using expected_exit_code by @jbedard in #2944

Full Changelog: v3.3.0...v3.3.1