-
Notifications
You must be signed in to change notification settings - Fork 134
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
Vote on namespace for args parser #1224
Comments
@nodejs/tsc FYI |
I personally think const args = process.parseArgs({
args: ["--some", ...otherArgs],
}); just doesn't seem right for something that has nothing to do with the current For something comparable, |
In most cases however, I wouldn't expect people to configure
Yea, I think |
If anything, imo |
Since it looks like there's consensus on what are the candidates for this vote, I went ahead and opened the voting PR: #1225 |
There was agreement today in the TSC meeting that we should start a vote on the question of which namespace parseArgs should go under as being discussed in nodejs/node#42675. Vote propsosed by @Trott and seconded by @mhdawson.
Since we did not have enough people in the meeting, this issue is to give other TSC members an FYI and time to comment/object.
The plan is to start the vote this Friday if there are no objections before then. @aduh95 volunteered to spin up the vote using his great tool.
The question for the vote is:
Should parseArgs be added under
The text was updated successfully, but these errors were encountered: