parseArgs Type Definition #47487

Activity

1. benjamingr commented on Apr 9, 2023

   

   benjamingr

   on Apr 9, 2023

   Member

   More actions

   cc @bcoe @RaisinTen @aduh95 (pinging Ben who added it and some people who reviewed that since I'm not sure what team to ping)
2. VoltrexKeyva

   added

   utilIssues and PRs related to the built-in util module.Issues and PRs related to the built-in util module.

   on Apr 9, 2023
3. shadowspawn commented on Apr 9, 2023

   

   shadowspawn

   on Apr 9, 2023

   Last edited by shadowspawn

   Member

   More actions

   Instead of having a type property with either a "string" or "boolean" value, I believe it would be more intuitive to have a boolean property with either true or false value, with the default value being false.

   This was deliberate in case there was expansion of types in the future or by third parties. The original design had a withValue array and the current naming was first discussed in refactor: pkgjs/parseargs#63 (comment)

   👍React with 👍1Reacted by Benjamin Gruenbaum
4. shadowspawn commented on Apr 9, 2023

   

   shadowspawn

   on Apr 9, 2023

   Last edited by shadowspawn

   Member

   More actions

   Furthermore, I would prefer the options to be an array of objects, as this would make it easier work with them.

   I think implicitly we were thinking of a key/value lookup of the options properties, but an array could work too. I think the difference is probably not compelling enough to change, also with parseArgs moving to stable in #46640

   Proposal for refactor leading to current configuration:
   pkgjs/parseargs#45

   Edit: Also I don't know if it would be possible to do the strong typing of the parse results in TypeScript if the options configuration was a plain array.

   👍React with 👍1Reacted by Benjamin Gruenbaum
5. shadowspawn commented on Apr 9, 2023

   

   shadowspawn

   on Apr 9, 2023

   Member

   More actions

   (Two good questions @marcobarriosfi )
6. benjamingr commented on Apr 10, 2023

   

   benjamingr

   on Apr 10, 2023

   Member

   More actions

   (The TS bit is possible to type though I actually personally like the current API better)

   👍React with 👍1Reacted by John Gee
7. github-actions commented on Jun 5, 2026

   

   github-actionsbot

   on Jun 5, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been marked as stale due to 210 days of inactivity.
   It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
8. github-actions

   added

   staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

   on Jun 5, 2026
9. github-actions commented on Jul 6, 2026

   

   github-actionsbot

   on Jul 6, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
   If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
10. github-actions

    closed this as not plannedon Jul 6, 2026