canirequire › ESM-only › @semantic-release/git
Is @semantic-release/git ESM-only? Can you require() it?
semantic-release plugin to commit release assets to the project's git repository
Last verified Sep 9, 2026 against @semantic-release/git@11.0.1. Markdown · JSON
ESM-only ESM-only since 11.0.0 — last CommonJS version is 10.0.1
@semantic-release/git dropped its CommonJS build in 11.0.0 (July 2026). The last version with a plain require()-able CommonJS entry is 10.0.1, published Oct 30, 2021; it declares support for Node.js >=14.17.
On Node.js 22.12+ and newer (@semantic-release/git@11.0.1 declares Node.js ^22.22.2 || >=24.15), require("@semantic-release/git") 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 @semantic-release/git@11.0.1 declares Node.js ^22.22.2 || >=24.15, so 18 is outside its supported range anyway.
@semantic-release/git@11.0.1 declares engines "^22.22.2 || >=24.15", so Node.js 18, 20 are outside its supported range regardless of module format.
What to do
- On Node.js 22.12+ and newer (@semantic-release/git@11.0.1 declares Node.js ^22.22.2 || >=24.15), require("@semantic-release/git") 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 git = await import("@semantic-release/git"). That works on every Node.js version the package supports (^22.22.2 || >=24.15).
- If you need a synchronous require() or run Node.js 18: npm install @semantic-release/git@10.0.1, the last CommonJS release (published Oct 30, 2021); it declares Node.js >=14.17.
- @semantic-release/git@11.0.1 declares engines "^22.22.2 || >=24.15", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
- TypeScript: no types are available for @semantic-release/git; declare the module yourself if you need them.
Does @semantic-release/git@11.0.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@semantic-release/git") from a CommonJS file and import "@semantic-release/git" from an ES module.
| Runtime | require("@semantic-release/git") | import "@semantic-release/git" |
|---|---|---|
| Node.js 18 | ✗ failsERR_REQUIRE_ESM | ✗ failsSyntaxError |
| Node.js 20 | ✗ failsTypeError | ✗ failsTypeError |
| 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/git
ES modules (import)
import * as git from "@semantic-release/git";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 git = require("@semantic-release/git");
// Any Node.js version the package supports (^22.22.2 || >=24.15), from an async function:
async function main() {
const git = await import("@semantic-release/git");
}
// Or pin the last CommonJS release (declares Node.js >=14.17):
// npm install @semantic-release/git@10.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 (46 versions; the newest 46 shown).
| Versions | Format | First published |
|---|---|---|
| 11.0.0 – 11.0.1 | ESM-only | Jul 21, 2026 |
| 1.0.0 – 10.0.1 | CommonJS | Dec 4, 2017 |
Frequently asked
Is @semantic-release/git ESM-only?
@semantic-release/git@11.0.1 is ESM-only. @semantic-release/git dropped its CommonJS build in 11.0.0 (July 2026). The last version with a plain require()-able CommonJS entry is 10.0.1, published Oct 30, 2021; it declares support for Node.js >=14.17.
Which version of @semantic-release/git still supports CommonJS / require()?
10.0.1 is the last version of @semantic-release/git with a CommonJS build; it declares Node.js >=14.17. Install it with "npm install @semantic-release/git@10.0.1". Every version from 11.0.0 on is ESM-only.
How do I use @semantic-release/git from a CommonJS file?
From a CommonJS file, use a dynamic import inside an async function: const git = await import("@semantic-release/git"). That works on every Node.js version the package supports (^22.22.2 || >=24.15). On Node.js 22.12+ and newer (@semantic-release/git@11.0.1 declares Node.js ^22.22.2 || >=24.15), require("@semantic-release/git") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Alternatively pin @semantic-release/git@10.0.1 (declares Node.js >=14.17).
Does @semantic-release/git work in Bun?
Yes. import "@semantic-release/git" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does @semantic-release/git ship TypeScript types?
No. @semantic-release/git 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
- @ethersproject/address 5.8.0CommonJS
- karma-jasmine 5.1.0CommonJS
- babel-polyfill 6.26.0CommonJS
- babel-plugin-transform-es2015-modules-commonjs 6.26.2CommonJS
- eslint-plugin-mocha 12.0.2ESM-only
- @babel/polyfill 7.12.1CommonJS
- async-validator 4.2.5CommonJS
- @ethersproject/networks 5.8.0CommonJS