-
Notifications
You must be signed in to change notification settings - Fork 520
Issues: bazel-contrib/rules_nodejs
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Bug]:
@nodejs//:node_bin does not resolve to the correct path in repository_rule
bug
#3809
opened Dec 14, 2024 by
allsey87
[Bug]: @bazel/runfiles does not work with non-bzlmod when a _repo_mapping file exists
bug
#3797
opened Oct 16, 2024 by
jbedard
[FR][Bug]: Split We have to do some design work in a meeting
@rules_nodejs//nodejs:toolchain_type to appropriately cover all use cases
enhancement
need: discussion
#3795
opened Oct 15, 2024 by
Silic0nS0ldier
[FR]: Provide codegen for We have to do some design work in a meeting
need: funding
We could prioritize this based on donation to https://opencollective.com/aspect-build
node_repositories value to simplify NodeJS upgrades
enhancement
need: discussion
#3782
opened Sep 2, 2024 by
Silic0nS0ldier
[FR]: Allow arbitrary NodeJS versions via bzlmod interface
enhancement
#3781
opened Sep 2, 2024 by
Silic0nS0ldier
[Bug]: We could prioritize this based on donation to https://opencollective.com/aspect-build
@bazel/runfiles should not throw an exception if used outside of a Bazel invocation
bug
enhancement
need: funding
#3770
opened Aug 7, 2024 by
shs96c
Replace use of Tech debt, resolving it improves our own velocity
bazel_tools/conditions with @platform
cleanup
ProTip!
Add no:assignee to see everything that’s not assigned.