-
Notifications
You must be signed in to change notification settings - Fork 521
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
feat: add npm binary & files to toolchain provider #3570
Conversation
3e2713c
to
ca0e82d
Compare
ca0e82d
to
c2e4f80
Compare
nodejs/toolchain.bzl
Outdated
@@ -89,6 +105,19 @@ node_toolchain = rule( | |||
doc = "Path to an existing nodejs executable for the target platform.", | |||
mandatory = False, | |||
), | |||
"npm": attr.label( | |||
doc = "A hermetically downloaded npm executable target for the target platform.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: should these really say for the "target platform"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, the node fields are target_tool
and target_tool_path
.
target_npm
, target_npm_path
and target_npm_files
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no I think the fields are named fine, it's just the docstring that's a tad misleading (for node as well - it was an existing problem here)
c2e4f80
to
ef88576
Compare
Downstream rules that use the toolchain can choose to include the npm binary & files specified by the toolchain as inputs for actions.