canirequire › CommonJS › @pkgjs/parseargs
Is @pkgjs/parseargs ESM-only? Can you require() it?
Polyfill of future proposal for `util.parseArgs()`
Last verified Sep 9, 2026 against @pkgjs/parseargs@0.11.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
@pkgjs/parseargs ships CommonJS only. require("@pkgjs/parseargs") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=14. import "@pkgjs/parseargs" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
What to do
- require("@pkgjs/parseargs") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=14.
- From ES modules use the default import: import parseargs from "@pkgjs/parseargs"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/pkgjs__parseargs
Does @pkgjs/parseargs@0.11.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@pkgjs/parseargs") from a CommonJS file and import "@pkgjs/parseargs" from an ES module.
| Runtime | require("@pkgjs/parseargs") | import "@pkgjs/parseargs" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4.0 | ✓ works | ✓ works |
How to import @pkgjs/parseargs
ES modules (import)
import parseargs from "@pkgjs/parseargs";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const parseargs = require("@pkgjs/parseargs");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (14 versions; the newest 14 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 0.11.0 | CommonJS | Jan 22, 2022 |
Frequently asked
Is @pkgjs/parseargs ESM-only?
@pkgjs/parseargs@0.11.0 is a CommonJS package. @pkgjs/parseargs ships CommonJS only. require("@pkgjs/parseargs") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=14. import "@pkgjs/parseargs" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import @pkgjs/parseargs with ES module syntax?
Yes. import parseargs from "@pkgjs/parseargs" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does @pkgjs/parseargs work in Bun?
Yes. import "@pkgjs/parseargs" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does @pkgjs/parseargs ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/pkgjs__parseargs".
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- tiny-invariant 1.3.3Dual
- @isaacs/cliui 9.0.0Dual
- @emnapi/runtime 1.11.3Dual
- is-negative-zero 2.0.3CommonJS
- @floating-ui/react-dom 2.1.9Dual
- for-each 0.3.5CommonJS
- normalize-path 3.0.0CommonJS
- is-set 2.0.3CommonJS