pkgjs/parseargs

Issues

• util.parseArgs being promoted from experimental to stable in NodeJs

  #149 opened 2 years ago by shadowspawn
  3

• Wrong license in `package.json`

  #153 opened 7 months ago by Joery-M
  1

• parseArgs in non-Node.js runtimes

  #152 opened 7 months ago by shadowspawn
  0

• 0.11.0 version has a package-lock.json dependency on a github repo

  #151 opened a year ago by denodaeus
  2

• `required` option

  #150 opened 2 years ago by Semigradsky
  3

• docs: better documentation of errors thrown on strict: true

  #148 opened 2 years ago by aarondill
  2

• Single dash options

  #147 opened 2 years ago by vjpr
  4

• TypeScript types

  #127 opened 2 years ago by bakkot
  28

• Second argument (first in `process.argv`) is always ignored.

  #146 opened 2 years ago by SpacingBat3
  5

• Reference specifications and implementations

  #76 opened 3 years ago by shadowspawn
  9

• How might I add support for defaults? (And env?)

  #82 opened 2 years ago by shadowspawn
  11

• docs: add strict:false example to upstream ?

  #114 opened 2 years ago by shadowspawn
  3

• What is happening with process.mainArgs?

  #128 opened 2 years ago by shadowspawn
  2

• Documentation tips for TypeScript

  #141 opened 2 years ago by shadowspawn
  1

• How might I add my own support for negative numbers?

  #72 opened 2 years ago by shadowspawn
  1

• stopping at first positional

  #125 opened 2 years ago by bakkot
  2

• make it possible to require long options with values use `=`

  #52 opened 2 years ago by ljharb
  11

• Reporting indexes

  #84 opened 2 years ago by bakkot
  21

• linter: our linter is missing some rules from the Node.js codebase

  #90 opened 3 years ago by bcoe
  3

• What's the minimum required Node.js version for this package?

  #131 opened 2 years ago by sodatea
  5

• Paranoia with Primordials

  #31 opened 3 years ago by shadowspawn
  4

• Committing not to ever use a `description` field / maybe reserving some other fields for future use

  #86 opened 3 years ago by bakkot
  3

• Syntax for combined short option and value

  #78 opened 3 years ago by shadowspawn
  2

• Thoughts, post MVP

  #124 opened 2 years ago by bcoe
  12

• Behavior of short with value including equals

  #126 opened 2 years ago by bcoe
  2

• Kudos Benjamin Coe

  #109 opened 2 years ago by shadowspawn
  2

• Unify custom error codes?

  #120 opened 2 years ago by shadowspawn
  4

• Restructure result conventions (again again)

  #119 opened 2 years ago by aaronccasanova
  6

• Survey of option-argument behaviours

  #79 opened 3 years ago by shadowspawn
  3

• Make "type: string" options greedy?

  #77 opened 3 years ago by shadowspawn
  21

• Should `positionals` be opt-in when `strict: true`?

  #85 opened 3 years ago by bakkot
  40

• null prototype for returned values?

  #108 opened 3 years ago by shadowspawn
  19

• Add placeholder for upstream docs?

  #107 opened 3 years ago by shadowspawn
  2

• More pollution protection?

  #104 opened 3 years ago by shadowspawn
  5

• Refactor tests?

  #105 opened 3 years ago by shadowspawn
  1

• security: switch to using Map during parsing

  #99 opened 3 years ago by bcoe
  4

• 🔨 Moving towards MVP Milestone 1

  #87 opened 3 years ago by shadowspawn
  6

• Restructure result conventions (again)

  #70 opened 3 years ago by shadowspawn
  29

• Make `type` mandatory for configured options

  #94 opened 3 years ago by bakkot
  2

• Paranoia with Prototype Pollution

  #32 opened 3 years ago by shadowspawn
  12

• Support for short options with numeric values, e.g, -p80

  #60 opened 3 years ago by bcoe
  9

• should "--" signal an end to parsing?

  #58 opened 3 years ago by bcoe
  4

• Improve API for configuring a high number of arguments

  #45 opened 3 years ago by aaronccasanova
  31

• Parse configuration: shorts better than short?

  #51 opened 3 years ago by shadowspawn
  10

• Multiple test files?

  #66 opened 3 years ago by shadowspawn
  2

• Propose stop storing explicit `undefined` in values for flags

  #55 opened 3 years ago by shadowspawn
  18

• Decide result conventions (includes detailed examples of client use)

  #38 opened 3 years ago by shadowspawn
  11

• withValue requires '=' for value to be set.

  #54 opened 3 years ago by bcoe
  4

• Tests style

  #30 opened 3 years ago by shadowspawn
  1

• Paranoia with null object

  #33 opened 3 years ago by shadowspawn
  7