canirequire

canirequire › CommonJS › @jest/globals

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

Last verified Sep 9, 2026 against @jest/globals@30.5.1. JSON

CommonJS CommonJS — require() works on every Node.js version

@jest/globals ships CommonJS only. require("@jest/globals") works everywhere. import "@jest/globals" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

Latest
30.5.1 (Sep 1, 2026)
Module format
CommonJS
Last CommonJS version
30.5.1
TypeScript types
Bundled
Node engines
^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0
License
MIT

Does @jest/globals@30.5.1 actually load? Runtime test results

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

Runtimerequire("@jest/globals")import "@jest/globals"
Node.js 18✗ failsError: Do not import `@jest/globals` outside of the Jest test environment✗ failsError: Do not import `@jest/globals` outside of the Jest test environment
Node.js 20✗ failsError: Do not import `@jest/globals` outside of the Jest test environment✗ failsError: Do not import `@jest/globals` outside of the Jest test environment
Node.js 22✗ failsError: Do not import `@jest/globals` outside of the Jest test environment✗ failsError: Do not import `@jest/globals` outside of the Jest test environment
Node.js 24✗ failsError: Do not import `@jest/globals` outside of the Jest test environment✗ failsError: Do not import `@jest/globals` outside of the Jest test environment
Node.js 26✗ failsError: Do not import `@jest/globals` outside of the Jest test environment✗ failsError: Do not import `@jest/globals` outside of the Jest test environment
Bun 1.4✗ failserror: Do not import `@jest/globals` outside of the Jest test environment✗ failserror: Do not import `@jest/globals` outside of the Jest test environment

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 @jest/globals

ES modules (import)

import globals from "@jest/globals";

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 globals = require("@jest/globals");

Module format by version

Derived from the type, main and exports fields of every stable release on npm (85 versions; the newest 60 shown).

VersionsFormatFirst published
27.2.1 – 30.5.1CommonJSSep 20, 2021

Frequently asked

Is @jest/globals ESM-only?

@jest/globals@30.5.1 is a CommonJS package. @jest/globals ships CommonJS only. require("@jest/globals") works everywhere. import "@jest/globals" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

Can I import @jest/globals with ES module syntax?

Yes. import globals from "@jest/globals" 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 @jest/globals work in Bun?

Importing @jest/globals failed in Bun 1.4 on Sep 9, 2026: error: Do not import `@jest/globals` outside of the Jest test environment

Does @jest/globals ship TypeScript types?

Yes. @jest/globals bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity