canirequire

canirequire › ESM-only › @semantic-release/npm

Is @semantic-release/npm ESM-only? Can you require() it?

semantic-release plugin to publish a npm package

Last verified Sep 9, 2026 against @semantic-release/npm@13.1.5. Markdown · JSON

ESM-only ESM-only since 10.0.0 — last CommonJS version is 9.0.2

@semantic-release/npm dropped its CommonJS build in 10.0.0 (March 2023). The last version with a plain require()-able CommonJS entry is 9.0.2, published Jan 13, 2023; it declares support for Node.js >=16 || ^14.17.

require("@semantic-release/npm") fails even on Node.js 22.12+ and newer: the package uses top-level await, which require(esm) cannot load (ERR_REQUIRE_ASYNC_MODULE). Use import() instead. Node.js 18 has no require(esm), and @semantic-release/npm@13.1.5 declares Node.js ^22.14.0 || >= 24.10.0, so 18 is outside its supported range anyway.

@semantic-release/npm@13.1.5 declares engines "^22.14.0 || >= 24.10.0", so Node.js 18, 20 are outside its supported range regardless of module format.

What to do

  1. require("@semantic-release/npm") fails even on Node.js 22.12+ and newer: the package uses top-level await, which require(esm) cannot load (ERR_REQUIRE_ASYNC_MODULE). Use import() instead.
  2. From a CommonJS file, use a dynamic import inside an async function: const npm = await import("@semantic-release/npm"). That works on every Node.js version the package supports (^22.14.0 || >= 24.10.0).
  3. If you need a synchronous require() or run Node.js 18: npm install @semantic-release/npm@9.0.2, the last CommonJS release (published Jan 13, 2023); it declares Node.js >=16 || ^14.17.
  4. @semantic-release/npm@13.1.5 declares engines "^22.14.0 || >= 24.10.0", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
  5. TypeScript: no types are available for @semantic-release/npm; declare the module yourself if you need them.
Latest
13.1.5 (Mar 1, 2026)
Module format
ESM-only
Last CommonJS version
9.0.2
ESM-only since
10.0.0 (Mar 22, 2023)
TypeScript types
None
Node engines
^22.14.0 || >= 24.10.0
Weekly downloads
2.8M
License
MIT

Does @semantic-release/npm@13.1.5 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("@semantic-release/npm") from a CommonJS file and import "@semantic-release/npm" from an ES module.

Runtimerequire("@semantic-release/npm")import "@semantic-release/npm"
Node.js 18✗ failsERR_REQUIRE_ESM✓ works
Node.js 20✗ failsERR_REQUIRE_ASYNC_MODULE✓ works
Node.js 22✗ failsERR_REQUIRE_ASYNC_MODULE✓ works
Node.js 24✗ failsERR_REQUIRE_ASYNC_MODULE✓ works
Node.js 26✗ failsERR_REQUIRE_ASYNC_MODULE✓ works
Bun 1.4.0✗ failsTypeError✓ works

How to import @semantic-release/npm

ES modules (import)

import * as npm from "@semantic-release/npm";

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 cannot require() this package: it uses top-level await.

// Any Node.js version the package supports (^22.14.0 || >= 24.10.0), from an async function:
async function main() {
  const npm = await import("@semantic-release/npm");
}

// Or pin the last CommonJS release (declares Node.js >=16 || ^14.17):
// npm install @semantic-release/npm@9.0.2

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

VersionsFormatFirst published
10.0.0 – 13.1.5ESM-onlyMar 22, 2023
5.1.7 – 9.0.2CommonJSApr 14, 2019

Frequently asked

Is @semantic-release/npm ESM-only?

@semantic-release/npm@13.1.5 is ESM-only. @semantic-release/npm dropped its CommonJS build in 10.0.0 (March 2023). The last version with a plain require()-able CommonJS entry is 9.0.2, published Jan 13, 2023; it declares support for Node.js >=16 || ^14.17.

Which version of @semantic-release/npm still supports CommonJS / require()?

9.0.2 is the last version of @semantic-release/npm with a CommonJS build; it declares Node.js >=16 || ^14.17. Install it with "npm install @semantic-release/npm@9.0.2". Every version from 10.0.0 on is ESM-only.

How do I use @semantic-release/npm from a CommonJS file?

From a CommonJS file, use a dynamic import inside an async function: const npm = await import("@semantic-release/npm"). That works on every Node.js version the package supports (^22.14.0 || >= 24.10.0). require("@semantic-release/npm") fails even on Node.js 22.12+ and newer: the package uses top-level await, which require(esm) cannot load (ERR_REQUIRE_ASYNC_MODULE). Use import() instead. Alternatively pin @semantic-release/npm@9.0.2 (declares Node.js >=16 || ^14.17).

Does @semantic-release/npm work in Bun?

Yes. import "@semantic-release/npm" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does @semantic-release/npm ship TypeScript types?

No. @semantic-release/npm ships no type declarations and there is no @types package for it.

Links

Other esm-only packages

Similar popularity