fix: check JS_BINARY__RUNFILES env variable in @bazel/runfiles helper
1 file changed
tree: 1be52338b650a418cb183fba1185d0d1ce5ca32d
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. .vscode/
  5. docs/
  6. e2e/
  7. external/
  8. internal/
  9. nodejs/
  10. packages/
  11. scripts/
  12. tools/
  13. .bazelignore
  14. .bazelrc
  15. .bazelversion
  16. .clang-format
  17. .git-blame-ignore-revs
  18. .gitignore
  19. .npmrc
  20. .pre-commit-config.yaml
  21. .prettierignore
  22. AUTHORS
  23. BUILD.bazel
  24. CHANGELOG.md
  25. CODE_OF_CONDUCT.md
  26. commitlint.config.js
  27. CONTRIBUTING.md
  28. CONTRIBUTORS
  29. DEVELOPING.md
  30. LICENSE
  31. MODULE.bazel
  32. package.json
  33. README.md
  34. renovate.json
  35. repositories.bzl
  36. WORKSPACE
  37. yarn.lock
README.md

JavaScript rules for Bazel

Build status GitHub release (latest by date)

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.

6.0 Scope Reduction

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.

Documentation

Comprehensive documentation for installing and using the rules, including generated API docs: https://bazelbuild.github.io/rules_nodejs/