canirequire › CommonJS › globals
Is globals ESM-only? Can you require() it?
Global identifiers from different JavaScript environments
Last verified Sep 9, 2026 against globals@17.12.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
globals ships CommonJS only. require("globals") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "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.
What to do
- require("globals") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.
- From ES modules use the default import: import globals from "globals"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does globals@17.12.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("globals") from a CommonJS file and import "globals" from an ES module.
| Runtime | require("globals") | import "globals" |
|---|---|---|
| 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.0 | ✓ works | ✓ works |
How to import globals
ES modules (import)
import globals from "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("globals");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 (142 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 13.2.0 – 17.12.0 | CommonJS | Aug 6, 2020 |
Frequently asked
Is globals ESM-only?
globals@17.12.0 is a CommonJS package. globals ships CommonJS only. require("globals") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "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 globals with ES module syntax?
Yes. import globals from "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 globals work in Bun?
Yes. import "globals" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does globals ship TypeScript types?
Yes. globals 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
- esbuild 0.28.2CommonJS
- ws 8.21.3Dual
- is-fullwidth-code-point 5.1.0ESM-only
- argparse 3.0.1CommonJS
- yargs 18.1.0ESM-only
- string_decoder 1.3.0CommonJS
- https-proxy-agent 9.1.0ESM-only
- js-tokens 10.0.0ESM-only