Skip to content

feat: add npm binary & files to toolchain provider - #3570

Merged
gregmagolan merged 1 commit into
stablefrom
opt_in_npm_in_toolchain
Oct 6, 2022
Merged

feat: add npm binary & files to toolchain provider#3570
gregmagolan merged 1 commit into
stablefrom
opt_in_npm_in_toolchain

Conversation

@gregmagolan

@gregmagolan gregmagolan commented Oct 6, 2022

Copy link
Copy Markdown
Collaborator

Downstream rules that use the toolchain can choose to include the npm binary & files specified by the toolchain as inputs for actions.

Comment thread nodejs/toolchain.bzl Outdated
mandatory = False,
),
"npm": attr.label(
doc = "A hermetically downloaded npm executable target for the target platform.",

Copy link
Copy Markdown
Collaborator

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"?

Copy link
Copy Markdown
Collaborator Author

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?

Copy link
Copy Markdown
Collaborator

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)

@gregmagolan
gregmagolan force-pushed the opt_in_npm_in_toolchain branch from c2e4f80 to ef88576 Compare October 6, 2022 18:55
@gregmagolan
gregmagolan merged commit 7ca0688 into stable Oct 6, 2022
@alexeagle
alexeagle deleted the opt_in_npm_in_toolchain branch October 6, 2022 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants