canirequire

canirequire › CommonJS › @babel/helper-globals

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

A collection of JavaScript globals for Babel internal usage

Last verified Sep 9, 2026 against @babel/helper-globals@8.0.0. Markdown · JSON

CommonJS CommonJS, subpaths only — require("@babel/helper-globals/…") works, require("@babel/helper-globals") does not

@babel/helper-globals exposes only subpaths in its exports map, for example "@babel/helper-globals/data/browser-upper.json"; there is no root entry, so require("@babel/helper-globals") and import "@babel/helper-globals" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("@babel/helper-globals/data/browser-upper.json") works everywhere, and import "@babel/helper-globals/data/browser-upper.json" works through Node's CommonJS interop.

What to do

  1. Load subpaths, never the bare name: const helperGlobals = require("@babel/helper-globals/data/browser-upper.json"). require("@babel/helper-globals") throws ERR_PACKAGE_PATH_NOT_EXPORTED.
  2. From ES modules use the default import: import helperGlobals from "@babel/helper-globals/data/browser-upper.json"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for @babel/helper-globals; declare the module yourself if you need them.
Latest
8.0.0 (Jun 16, 2026)
Module format
CommonJS
Last CommonJS version
8.0.0
TypeScript types
None
Node engines
^22.18.0 || >=24.11.0
Weekly downloads
140.7M
License
MIT

Does @babel/helper-globals@8.0.0 actually load? Runtime test results

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

Runtimerequire("@babel/helper-globals")import "@babel/helper-globals"
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/helper-globals

ES modules (import)

import helperGlobals from "@babel/helper-globals/data/browser-upper.json";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const helperGlobals = require("@babel/helper-globals/data/browser-upper.json");

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

VersionsFormatFirst published
7.28.0 – 8.0.0CommonJSJul 2, 2025

Frequently asked

Is @babel/helper-globals ESM-only?

@babel/helper-globals@8.0.0 is a CommonJS package, reachable only through subpaths. @babel/helper-globals exposes only subpaths in its exports map, for example "@babel/helper-globals/data/browser-upper.json"; there is no root entry, so require("@babel/helper-globals") and import "@babel/helper-globals" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("@babel/helper-globals/data/browser-upper.json") works everywhere, and import "@babel/helper-globals/data/browser-upper.json" works through Node's CommonJS interop.

Can I require @babel/helper-globals?

Only by subpath. require("@babel/helper-globals") throws ERR_PACKAGE_PATH_NOT_EXPORTED because the exports map has no root entry; require("@babel/helper-globals/data/browser-upper.json") works.

Can I import @babel/helper-globals with ES module syntax?

Yes. import helperGlobals from "@babel/helper-globals/data/browser-upper.json" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

Does @babel/helper-globals work in Bun?

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

Does @babel/helper-globals ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity