canirequire

canirequire › CommonJS › progress

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

Flexible ascii progress bar

Last verified Sep 9, 2026 against progress@2.0.3. Markdown · JSON

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

progress ships CommonJS only. require("progress") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=0.4.0. import "progress" 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("progress") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=0.4.0.
  2. From ES modules use the default import: import progress from "progress"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: npm install -D @types/progress
Latest
2.0.3 (Dec 5, 2018)
Module format
CommonJS
Last CommonJS version
2.0.3
TypeScript types
@types/progress
Node engines
>=0.4.0
Weekly downloads
49.1M
License
MIT

Does progress@2.0.3 actually load? Runtime test results

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

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

ES modules (import)

import progress from "progress";

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

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

VersionsFormatFirst published
0.0.1 – 2.0.3CommonJSApr 20, 2011

Frequently asked

Is progress ESM-only?

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

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

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

Does progress ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity