canirequire

canirequire › CommonJS › nopt

Is nopt ESM-only? Can you require() it?

Option parsing for Node, supporting types, shorthands, etc. Used by npm.

Last verified Sep 9, 2026 against nopt@10.0.1. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

nopt ships CommonJS only. require("nopt") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.22.2 || ^24.15.0 || >=26.0.0. import "nopt" 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

  1. require("nopt") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.22.2 || ^24.15.0 || >=26.0.0.
  2. From ES modules use the default import: import nopt from "nopt"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: npm install -D @types/nopt
Latest
10.0.1 (Jun 4, 2026)
Module format
CommonJS
Last CommonJS version
10.0.1
TypeScript types
@types/nopt
Node engines
^22.22.2 || ^24.15.0 || >=26.0.0
Weekly downloads
67.7M
License
ISC

Does nopt@10.0.1 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("nopt") from a CommonJS file and import "nopt" from an ES module.

Runtimerequire("nopt")import "nopt"
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 nopt

ES modules (import)

import nopt from "nopt";

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 nopt = require("nopt");

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 (39 versions; the newest 39 shown).

VersionsFormatFirst published
1.0.0 – 10.0.1CommonJSMar 30, 2011

Frequently asked

Is nopt ESM-only?

nopt@10.0.1 is a CommonJS package. nopt ships CommonJS only. require("nopt") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.22.2 || ^24.15.0 || >=26.0.0. import "nopt" 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 nopt with ES module syntax?

Yes. import nopt from "nopt" 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 nopt work in Bun?

Yes. import "nopt" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does nopt ship TypeScript types?

Not bundled. Install the community types with "npm install -D @types/nopt".

Links

Other commonjs packages

Similar popularity