-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Request: mark util.parseArgs() as stable #46640
Labels
feature request
Issues that request new features to be added to Node.js.
util
Issues and PRs related to the built-in util module.
Comments
cjihrig
added
the
feature request
Issues that request new features to be added to Node.js.
label
Feb 13, 2023
+1 |
@nodejs/tooling |
+1 |
1 similar comment
+1 |
+1 |
+1 |
cjihrig
added a commit
to cjihrig/node
that referenced
this issue
Feb 18, 2023
cjihrig
added a commit
to cjihrig/node
that referenced
this issue
Feb 18, 2023
+1 |
nodejs-github-bot
pushed a commit
that referenced
this issue
Feb 21, 2023
Fixes: #46640 PR-URL: #46718 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]>
+1 (Exciting! Woop woop!) |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature request
Issues that request new features to be added to Node.js.
util
Issues and PRs related to the built-in util module.
What is the problem this feature will solve?
I am opening this issue to gauge how close we might be to stabilizing
util.parseArgs()
. I haven't seen a ton of development on it recently, and stable doesn't have to mean finished.What is the feature you are proposing to solve the problem?
Stabilizing
util.parseArgs()
if the folks working on it think it's ready.What alternatives have you considered?
Leaving things as is.
The text was updated successfully, but these errors were encountered: