canirequire › CommonJS › @jest/environment
Is @jest/environment ESM-only? Can you require() it?
Last verified Sep 9, 2026 against @jest/environment@30.5.1. JSON
CommonJS CommonJS — require() works on every Node.js version
@jest/environment ships CommonJS only. require("@jest/environment") works everywhere. import "@jest/environment" 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.
Does @jest/environment@30.5.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@jest/environment") from a CommonJS file and import "@jest/environment" from an ES module.
| Runtime | require("@jest/environment") | import "@jest/environment" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4 | ✓ works | ✓ works |
How to import @jest/environment
ES modules (import)
import environment from "@jest/environment";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 environment = require("@jest/environment");Module format by version
Derived from the type, main and exports fields of every stable release on npm (95 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 27.1.0 – 30.5.1 | CommonJS | Aug 27, 2021 |
Frequently asked
Is @jest/environment ESM-only?
@jest/environment@30.5.1 is a CommonJS package. @jest/environment ships CommonJS only. require("@jest/environment") works everywhere. import "@jest/environment" 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/environment with ES module syntax?
Yes. import environment from "@jest/environment" 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/environment work in Bun?
Yes. import "@jest/environment" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @jest/environment ship TypeScript types?
Yes. @jest/environment bundles its own type declarations; no @types package is needed.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @img/sharp-linux-x64 0.35.4CommonJS
- @babel/plugin-syntax-import-attributes 7.29.7CommonJS
- @babel/helper-create-class-features-plugin 8.0.1ESM-only
- @radix-ui/react-roving-focus 1.1.19Dual
- @vitest/mocker 5.0.0ESM-only
- @smithy/util-middleware 4.5.2CommonJS
- @aws-sdk/region-config-resolver 3.972.48CommonJS
- @aws-sdk/util-user-agent-browser 3.972.45CommonJS