Skip to content

issues Search Results · repo:pkgjs/parseargs language:JavaScript

Filter by

69 results
 (52 ms)

69 results

inpkgjs/parseargs (press backspace or delete to remove)

pkgjs/parseargs
Wrong license spdx (MIT instead of Apache-2.0) is shown in the npmjs.com repository

In the metadata shown in the npmjs.com repository of this component is wrong (MIT instead of Apache-2.0). If you display the license file (shown at code link) the correct license file is attached. == ...
  • johannesstellnberger
  • 5
  • Opened 
    on Jan 28
  • #162

pkgjs/parseargs
Tidelift

I was wondering whether to do more work here as fairly quiet and question whether should be archived (https://github.com/pkgjs/parseargs/issues/149#issuecomment-2160058600), but a surprising number of ...
  • shadowspawn
  • 6
  • Opened 
    on Jan 16
  • #161

pkgjs/parseargs
need to implement `allowNegative` option

node has this; added in https://github.com/nodejs/node/pull/53107 This package should too.
  • ljharb
  • Opened 
    on Dec 28, 2024
  • #160

pkgjs/parseargs
parseArgs in runtimes where `global` is not defined

This module is useful as a polyfill for older Node versions. But it could also be useful for other runtimes, such as gjs, that may not want to implement a Node compatibility layer but nevertheless would ...
  • kisaragi-hiu
  • 3
  • Opened 
    on Sep 7, 2024
  • #157

pkgjs/parseargs
Wrong license in `package.json`

The license field of package.json is MIT, but Apache-2.0 is defined in the LICENSE file. Now this usually wouldn t matter, since the licenses are similar (for the most part). But tools like pnpm-licenses ...
  • Joery-M
  • 1
  • Opened 
    on Mar 16, 2024
  • #153

pkgjs/parseargs
parseArgs in non-Node.js runtimes

Fun to see parseArgs appearing in other runtimes as they expand node compatibility. // parseargs.ts import { parseArgs } from node:util ; console.log(parseArgs({ strict: false })); % bun run parseargs.ts ...
  • shadowspawn
  • Opened 
    on Mar 8, 2024
  • #152

pkgjs/parseargs
0.11.0 version has a package-lock.json dependency on a github repo

Several people (like myself) use artifactory as a proxy through to npm as our CI s don t have public internet access. This makes resolving dependencies like the below impossible. Can you change this to ...
  • denodaeus
  • 2
  • Opened 
    on May 1, 2023
  • #151

pkgjs/parseargs
`required` option

Currently, Node.js is checking that arg has the correct type (by the strict option). By I need manually check that this arg was provided by user. How about boolean flag required for this? Before: const ...
  • Semigradsky
  • 3
  • Opened 
    on Apr 14, 2023
  • #150

pkgjs/parseargs
util.parseArgs being promoted from experimental to stable in NodeJs

Proposal to move util.parseArgs to stable: https://github.com/nodejs/node/issues/46640 There may still be some interested experts watching this repo, but future development is likely to be directly in ...
  • shadowspawn
  • 3
  • Opened 
    on Feb 25, 2023
  • #149

pkgjs/parseargs
docs: better documentation of errors thrown on strict: true

The documentation for strict: true says that it throws an error, but says nothing about the possible error.codes. Increased documentation would make displaying help and errors to users far easier to figure ...
documentation
  • aarondill
  • 2
  • Opened 
    on Feb 2, 2023
  • #148
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub