canirequire

canirequire › ESM-only › content-type

Is content-type ESM-only? Can you require() it?

Create and parse HTTP Content-Type header

Last verified Sep 9, 2026 against content-type@3.0.0. Markdown · JSON

ESM-only ESM-only since 3.0.0 — last CommonJS version is 2.1.0

content-type dropped its CommonJS build in 3.0.0 (August 2026). The last version with a plain require()-able CommonJS entry is 2.1.0, published Aug 13, 2026; it declares support for Node.js >=18.

On Node.js 22.12+ and newer (content-type@3.0.0 declares Node.js >=22), require("content-type") 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-type@3.0.0 declares Node.js >=22, so 18 is outside its supported range anyway.

content-type@3.0.0 declares engines ">=22", so Node.js 18, 20 are outside its supported range regardless of module format.

What to do

  1. On Node.js 22.12+ and newer (content-type@3.0.0 declares Node.js >=22), require("content-type") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26.
  2. From a CommonJS file, use a dynamic import inside an async function: const contentType = await import("content-type"). That works on every Node.js version the package supports (>=22).
  3. If you need a synchronous require() or run Node.js 18: npm install content-type@2.1.0, the last CommonJS release (published Aug 13, 2026); it declares Node.js >=18.
  4. content-type@3.0.0 declares engines ">=22", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
  5. TypeScript: types are bundled; install nothing extra.
Latest
3.0.0 (Aug 20, 2026)
Module format
ESM-only
Last CommonJS version
2.1.0
ESM-only since
3.0.0 (Aug 20, 2026)
TypeScript types
Bundled
Node engines
>=22
Weekly downloads
191.4M
License
MIT

Does content-type@3.0.0 actually load? Runtime test results

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

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

ES modules (import)

import * as contentType from "content-type";

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 contentType = require("content-type");

// Any Node.js version the package supports (>=22), from an async function:
async function main() {
  const contentType = await import("content-type");
}

// Or pin the last CommonJS release (declares Node.js >=18):
// npm install content-type@2.1.0

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

VersionsFormatFirst published
3.0.0ESM-onlyAug 20, 2026
0.0.1 – 2.1.0CommonJSOct 8, 2013

Frequently asked

Is content-type ESM-only?

content-type@3.0.0 is ESM-only. content-type dropped its CommonJS build in 3.0.0 (August 2026). The last version with a plain require()-able CommonJS entry is 2.1.0, published Aug 13, 2026; it declares support for Node.js >=18.

Which version of content-type still supports CommonJS / require()?

2.1.0 is the last version of content-type with a CommonJS build; it declares Node.js >=18. Install it with "npm install content-type@2.1.0". Every version from 3.0.0 on is ESM-only.

How do I use content-type from a CommonJS file?

From a CommonJS file, use a dynamic import inside an async function: const contentType = await import("content-type"). That works on every Node.js version the package supports (>=22). On Node.js 22.12+ and newer (content-type@3.0.0 declares Node.js >=22), require("content-type") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Alternatively pin content-type@2.1.0 (declares Node.js >=18).

Does content-type work in Bun?

Yes. import "content-type" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does content-type ship TypeScript types?

Yes. content-type bundles its own type declarations; no @types package is needed.

Links

Other esm-only packages

Similar popularity