canirequire

canirequire › Dual (CommonJS + ESM) › @babel/runtime

Is @babel/runtime ESM-only? Can you require() it?

babel's modular runtime helpers

Last verified Sep 9, 2026 against @babel/runtime@8.0.0. Markdown · JSON

Dual (CommonJS + ESM) Dual package, subpaths only — require("@babel/runtime/…") works, require("@babel/runtime") does not

@babel/runtime exposes only subpaths in its exports map, for example "@babel/runtime/helpers/get"; there is no root entry, so require("@babel/runtime") and import "@babel/runtime" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. Each subpath ships a CommonJS and a native ESM build, so require("@babel/runtime/helpers/get") and import "@babel/runtime/helpers/get" both work.

What to do

  1. Load subpaths, never the bare name: const runtime = require("@babel/runtime/helpers/get") or import from "@babel/runtime/helpers/get". require("@babel/runtime") throws ERR_PACKAGE_PATH_NOT_EXPORTED.
  2. TypeScript: no types are available for @babel/runtime; declare the module yourself if you need them.
Latest
8.0.0 (Jun 16, 2026)
Module format
Dual (CommonJS + ESM)
Last CommonJS version
8.0.0
Native ESM since
7.13.0
TypeScript types
None
Node engines
not declared
Weekly downloads
134.1M
License
MIT

Does @babel/runtime@8.0.0 actually load? Runtime test results

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

Runtimerequire("@babel/runtime")import "@babel/runtime"
Node.js 18✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 20✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 22✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 24✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 26✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Bun 1.4.0✗ failsError✗ failsError

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import @babel/runtime

ES modules (import)

import * as runtime from "@babel/runtime/helpers/get";

Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.

CommonJS (require)

const runtime = require("@babel/runtime/helpers/get");

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

VersionsFormatFirst published
7.17.9 – 8.0.0Dual (CommonJS + ESM)Apr 6, 2022

Frequently asked

Is @babel/runtime ESM-only?

@babel/runtime@8.0.0 ships CommonJS and ESM builds, reachable only through subpaths. @babel/runtime exposes only subpaths in its exports map, for example "@babel/runtime/helpers/get"; there is no root entry, so require("@babel/runtime") and import "@babel/runtime" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. Each subpath ships a CommonJS and a native ESM build, so require("@babel/runtime/helpers/get") and import "@babel/runtime/helpers/get" both work.

Can I require @babel/runtime?

Only by subpath. require("@babel/runtime") throws ERR_PACKAGE_PATH_NOT_EXPORTED because the exports map has no root entry; require("@babel/runtime/helpers/get") works, and so does import from the same subpath.

Does @babel/runtime work in Bun?

Importing @babel/runtime failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@babel/runtime' from '/Users/boat/Projects/top-seo/data/probe-work/@babel__runtime/imp.mjs'

Does @babel/runtime ship TypeScript types?

No. @babel/runtime ships no type declarations and there is no @types package for it.

Links

Other dual (commonjs + esm) packages

Similar popularity