Issues

• Consider adopting npm trusted publishing

  pkgjs/parseargs#164 · Filter by author JamieMagee opened on Sep 27, 2025
  12

• Wrong license in package.json

  pkgjs/parseargs#153 · Filter by author Joery-M opened on Mar 16, 2024
  1

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

  pkgjs/parseargs#151 · Filter by author denodaeus opened on May 1, 2023
  2

• required option

  pkgjs/parseargs#150 · Filter by author Semigradsky opened on Apr 14, 2023
  3

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

  documentation
  pkgjs/parseargs#148 · Filter by author aarondill opened on Feb 2, 2023
  2

• Documentation tips for TypeScript

  pkgjs/parseargs#141 · Filter by author shadowspawn opened on Aug 11, 2022
  1

• TypeScript types

  help wanted
  pkgjs/parseargs#127 · Filter by author bakkot opened on May 26, 2022
  28

• Behavior of short with value including equals

  question
  pkgjs/parseargs#126 · Filter by author bcoe opened on May 26, 2022
  2

• stopping at first positional

  enhancement
  pkgjs/parseargs#125 · Filter by author bakkot opened on May 25, 2022
  2

• Thoughts, post MVP

  discussion
  pkgjs/parseargs#124 · Filter by author bcoe opened on May 23, 2022
  12

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

  enhancement
  pkgjs/parseargs#90 · Filter by author bcoe opened on Apr 9, 2022
  3

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

  discussion
  pkgjs/parseargs#86 · Filter by author bakkot opened on Mar 20, 2022
  3

• Survey of option-argument behaviours

  pkgjs/parseargs#79 · Filter by author shadowspawn opened on Mar 12, 2022
  3

• Reference specifications and implementations

  pkgjs/parseargs#76 · Filter by author shadowspawn opened on Mar 6, 2022
  9