| commit | 82738bd4783943e42c68eca5061dcdc33577d401 | [log] [tgz] |
|---|---|---|
| author | Gunnar Wagenknecht <gunnar@wagenknecht.org> | Tue Oct 21 19:42:36 2025 +0200 |
| committer | GitHub <noreply@github.com> | Tue Oct 21 10:42:36 2025 -0700 |
| tree | dba5dfe3fbfbdaa872047d27986aef14aac5ad6e | |
| parent | 3fdfd02f6a5f8677bc323eeba1b9e97128ba3e00 [diff] |
Introduce runtime_toolchain_type (#3859) According to discussions in #3854 having two toolchains of the same type for different things is troublesome. It's better to have separate runtime as well as compile toolchains. This commit creates a new runtime_toolchain_type and registers toolchains without execution constraints for this type. Once merged, rules_ts can start consuming the new toolchain type in its js_binary rule to ensure the correct Node for the correct target environment is selected. Fixed [Bug]: Execution toolchain defined without `target_compatible_with` makes it a candidate to selection Fixes #3854 Work towards #3795 ## PR Checklist Please check if your PR fulfills the following requirements: - [x] Tests for the changes have been added (for bug fixes / features) - [x] Docs have been added / updated (for bug fixes / features) ## PR Type What kind of change does this PR introduce? <!-- Please check the one that applies to this PR using "x". --> - [x] Bugfix - [x] Feature (please, look at the "Scope of the project" section in the README.md file) - [x] Documentation content changes ## Does this PR introduce a breaking change? - [ ] Yes - [x] No It tries to remain compatible and support existing consumers. ## Other information This is an alternative to #3800.
This ruleset provides a Node.js development toolchain and runtime with Bazel. It does not have any rules for using Node.js, such as nodejs_binary. For that, we recommend rules_js.
This repository is maintained by volunteers in the Bazel community. Neither Google, nor the Bazel team, provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases.
We follow semantic versioning. Patch releases have bugfixes, minor releases have new features. Only major releases (1.x, 2.x) have breaking changes. We support LTS releases of Bazel (starting at 4.x), see SUPPORTED_BAZEL_VERSIONS in our /index.bzl for the list we test against.
This branch is the latest release, 6.x.x It has a greatly reduced scope from previous releases, as most of the code was unmaintained. See the 5.x branch for the prior state of the repo.
See the docs/ folder, and generated API docs on https://registry.bazel.build/docs/rules_nodejs
