canirequire › ESM-only › content-disposition
Is content-disposition ESM-only? Can you require() it?
Create and parse Content-Disposition header
Last verified Sep 9, 2026 against content-disposition@3.0.0. Markdown · JSON
ESM-only ESM-only since 3.0.0 — last CommonJS version is 2.0.1
content-disposition dropped its CommonJS build in 3.0.0 (August 2026). The last version with a plain require()-able CommonJS entry is 2.0.1, published May 28, 2026; it declares support for Node.js >=18.
On Node.js 22.12+ and newer (content-disposition@3.0.0 declares Node.js >=22), require("content-disposition") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Node.js 18 has no require(esm), and content-disposition@3.0.0 declares Node.js >=22, so 18 is outside its supported range anyway.
content-disposition@3.0.0 declares engines ">=22", so Node.js 18, 20 are outside its supported range regardless of module format.
What to do
- On Node.js 22.12+ and newer (content-disposition@3.0.0 declares Node.js >=22), require("content-disposition") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26.
- From a CommonJS file, use a dynamic import inside an async function: const contentDisposition = await import("content-disposition"). That works on every Node.js version the package supports (>=22).
- If you need a synchronous require() or run Node.js 18: npm install content-disposition@2.0.1, the last CommonJS release (published May 28, 2026); it declares Node.js >=18.
- content-disposition@3.0.0 declares engines ">=22", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
- TypeScript: types are bundled; install nothing extra.
Does content-disposition@3.0.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("content-disposition") from a CommonJS file and import "content-disposition" from an ES module.
| Runtime | require("content-disposition") | import "content-disposition" |
|---|---|---|
| Node.js 18 | ✗ failsERR_REQUIRE_ESM | ✓ 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 content-disposition
ES modules (import)
import * as contentDisposition from "content-disposition";Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.
CommonJS (require)
// Node.js 22.12+ and newer (verified):
const contentDisposition = require("content-disposition");
// Any Node.js version the package supports (>=22), from an async function:
async function main() {
const contentDisposition = await import("content-disposition");
}
// Or pin the last CommonJS release (declares Node.js >=18):
// npm install content-disposition@2.0.1Module 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 (18 versions; the newest 18 shown).
| Versions | Format | First published |
|---|---|---|
| 3.0.0 | ESM-only | Aug 13, 2026 |
| 0.0.0 – 2.0.1 | CommonJS | Sep 19, 2014 |
Frequently asked
Is content-disposition ESM-only?
content-disposition@3.0.0 is ESM-only. content-disposition dropped its CommonJS build in 3.0.0 (August 2026). The last version with a plain require()-able CommonJS entry is 2.0.1, published May 28, 2026; it declares support for Node.js >=18.
Which version of content-disposition still supports CommonJS / require()?
2.0.1 is the last version of content-disposition with a CommonJS build; it declares Node.js >=18. Install it with "npm install content-disposition@2.0.1". Every version from 3.0.0 on is ESM-only.
How do I use content-disposition from a CommonJS file?
From a CommonJS file, use a dynamic import inside an async function: const contentDisposition = await import("content-disposition"). That works on every Node.js version the package supports (>=22). On Node.js 22.12+ and newer (content-disposition@3.0.0 declares Node.js >=22), require("content-disposition") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Alternatively pin content-disposition@2.0.1 (declares Node.js >=18).
Does content-disposition work in Bun?
Yes. import "content-disposition" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does content-disposition ship TypeScript types?
Yes. content-disposition bundles its own type declarations; no @types package is needed.
Links
Other esm-only packages
- ansi-styles 7.0.0last CJS
5.2.0 - strip-ansi 7.2.0last CJS
6.0.1 - commander 15.0.0last CJS
14.0.3 - supports-color 11.0.0last CJS
8.1.1 - chalk 6.0.0last CJS
4.1.2 - string-width 8.2.2last CJS
4.2.3 - ansi-regex 6.3.0last CJS
5.0.1 - escape-string-regexp 5.0.0last CJS
4.0.0
Similar popularity
- lightningcss 1.33.0Dual
- raw-body 4.0.0ESM-only
- @opentelemetry/core 2.11.0CommonJS
- @typescript-eslint/types 8.70.0CommonJS
- gensync 1.0.0-beta.2CommonJS
- send 1.2.1CommonJS
- y18n 5.0.8Dual
- path-scurry 2.0.2Dual