canirequire › ESM-only › @semantic-release/commit-analyzer
Is @semantic-release/commit-analyzer ESM-only? Can you require() it?
semantic-release plugin to analyze commits with conventional-changelog
Last verified Sep 9, 2026 against @semantic-release/commit-analyzer@13.0.1. Markdown · JSON
ESM-only ESM-only since 10.0.0 — last CommonJS version is 9.0.2
@semantic-release/commit-analyzer dropped its CommonJS build in 10.0.0 (June 2023). The last version with a plain require()-able CommonJS entry is 9.0.2, published Nov 23, 2021; it declares support for Node.js >=14.17.
On Node.js 20.19+, 22.12+ and newer, require("@semantic-release/commit-analyzer") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Node.js 18 has no require(esm), and @semantic-release/commit-analyzer@13.0.1 declares Node.js >=20.8.1, so 18 is outside its supported range anyway.
@semantic-release/commit-analyzer@13.0.1 declares engines ">=20.8.1", so Node.js 18 is outside its supported range regardless of module format.
What to do
- On Node.js 20.19+, 22.12+ and newer, require("@semantic-release/commit-analyzer") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26.
- From a CommonJS file, use a dynamic import inside an async function: const commitAnalyzer = await import("@semantic-release/commit-analyzer"). That works on every Node.js version the package supports (>=20.8.1).
- If you need a synchronous require() or run Node.js 18: npm install @semantic-release/commit-analyzer@9.0.2, the last CommonJS release (published Nov 23, 2021); it declares Node.js >=14.17.
- @semantic-release/commit-analyzer@13.0.1 declares engines ">=20.8.1", so Node.js 18 is unsupported regardless: upgrade Node.js or pin an older release.
- TypeScript: no types are available for @semantic-release/commit-analyzer; declare the module yourself if you need them.
Does @semantic-release/commit-analyzer@13.0.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@semantic-release/commit-analyzer") from a CommonJS file and import "@semantic-release/commit-analyzer" from an ES module.
| Runtime | require("@semantic-release/commit-analyzer") | import "@semantic-release/commit-analyzer" |
|---|---|---|
| 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 @semantic-release/commit-analyzer
ES modules (import)
import * as commitAnalyzer from "@semantic-release/commit-analyzer";Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.
CommonJS (require)
// Node.js 20.19+, 22.12+ and newer (verified):
const commitAnalyzer = require("@semantic-release/commit-analyzer");
// Any Node.js version the package supports (>=20.8.1), from an async function:
async function main() {
const commitAnalyzer = await import("@semantic-release/commit-analyzer");
}
// Or pin the last CommonJS release (declares Node.js >=14.17):
// npm install @semantic-release/commit-analyzer@9.0.2Module 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 (44 versions; the newest 44 shown).
| Versions | Format | First published |
|---|---|---|
| 10.0.0 – 13.0.1 | ESM-only | Jun 2, 2023 |
| 1.0.0 – 9.0.2 | CommonJS | Jun 19, 2015 |
Frequently asked
Is @semantic-release/commit-analyzer ESM-only?
@semantic-release/commit-analyzer@13.0.1 is ESM-only. @semantic-release/commit-analyzer dropped its CommonJS build in 10.0.0 (June 2023). The last version with a plain require()-able CommonJS entry is 9.0.2, published Nov 23, 2021; it declares support for Node.js >=14.17.
Which version of @semantic-release/commit-analyzer still supports CommonJS / require()?
9.0.2 is the last version of @semantic-release/commit-analyzer with a CommonJS build; it declares Node.js >=14.17. Install it with "npm install @semantic-release/commit-analyzer@9.0.2". Every version from 10.0.0 on is ESM-only.
How do I use @semantic-release/commit-analyzer from a CommonJS file?
From a CommonJS file, use a dynamic import inside an async function: const commitAnalyzer = await import("@semantic-release/commit-analyzer"). That works on every Node.js version the package supports (>=20.8.1). On Node.js 20.19+, 22.12+ and newer, require("@semantic-release/commit-analyzer") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Alternatively pin @semantic-release/commit-analyzer@9.0.2 (declares Node.js >=14.17).
Does @semantic-release/commit-analyzer work in Bun?
Yes. import "@semantic-release/commit-analyzer" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does @semantic-release/commit-analyzer ship TypeScript types?
No. @semantic-release/commit-analyzer ships no type declarations and there is no @types package for it.
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
- @semantic-release/npm 13.1.5ESM-only
- react-intl 10.1.26ESM-only
- bunyan 1.8.15CommonJS
- karma-chrome-launcher 3.2.0CommonJS
- optimist 0.6.1CommonJS
- jsdoc 4.0.5No entry
- stylus 0.64.0CommonJS
- babel-plugin-named-asset-import 0.3.8CommonJS