-
Notifications
You must be signed in to change notification settings - Fork 10
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
What is happening with process.mainArgs? #128
Comments
There's another benefit specifically for |
This hasn't got additional interest (thanks for comment @bakkot) and isn't likely to get championed out of this project. The Tooling Group is a more likely place to gather interest. |
The README includes mention of a proposal for
process.mainsArgs
. Is there still interest in that as a separate proposal, or diminishing returns afterparseArgs
?I see two possible benefits from
process.mainArgs
:process.mainArgs
in author friendly way, compared withprocess.argv
which sometimes breaks Node.js conventions (e.g. Electron, zx). This is a speculative benefit which may not eventuate!If
process.mainArgs
is unlikely, then it is a decision forparseArgs
alone whether to expose the implicit args in context of richer parsing information (#84 (comment), #84 (comment), #84 (comment)).I think
process.mainArgs
was first suggested in argument parsing thread: nodejs/tooling#19 (comment)This later comment follows up on a meeting and agrees with dropping
process.mainArgs
and focus on argument parsing : nodejs/tooling#19 (comment)The text was updated successfully, but these errors were encountered: