canirequire › CommonJS › process
Is process ESM-only? Can you require() it?
process information for node.js and browsers
Last verified Sep 9, 2026 against process@0.11.10. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
process ships CommonJS only. require("process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.6.0. import "process" 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("process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.6.0.
- From ES modules use the default import: import process from "process"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for process; declare the module yourself if you need them.
Does process@0.11.10 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("process") from a CommonJS file and import "process" from an ES module.
| Runtime | require("process") | import "process" |
|---|---|---|
| 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 process
ES modules (import)
import process from "process";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 process = require("process");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 (21 versions; the newest 21 shown).
| Versions | Format | First published |
|---|---|---|
| 0.4.9 – 0.11.10 | CommonJS | Jun 30, 2011 |
Frequently asked
Is process ESM-only?
process@0.11.10 is a CommonJS package. process ships CommonJS only. require("process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.6.0. import "process" 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 process with ES module syntax?
Yes. import process from "process" 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 process work in Bun?
Yes. import "process" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does process ship TypeScript types?
No. process ships no type declarations and there is no @types package for it.
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
- @testing-library/react 16.3.3CommonJS
- @aws-sdk/middleware-host-header 3.972.45CommonJS
- file-type 22.0.2ESM-only
- cli-spinners 3.4.0ESM-only
- @radix-ui/react-progress 1.1.16Dual
- package-json-from-dist 1.0.1Dual
- terser-webpack-plugin 5.6.1CommonJS
- @radix-ui/react-scroll-area 1.2.18Dual