canirequire

canirequire › CommonJS › child_process

Is child_process ESM-only? Can you require() it?

This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.

Last verified Sep 9, 2026 against child_process@1.0.2. Markdown · JSON

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

child_process ships CommonJS only. require("child_process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "child_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

  1. require("child_process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
  2. From ES modules use the default import: import childProcess from "child_process"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for child_process; declare the module yourself if you need them.
Latest
1.0.2 (Aug 26, 2016)
Module format
CommonJS
Last CommonJS version
1.0.2
TypeScript types
None
Node engines
not declared
Weekly downloads
151K
License
ISC

Does child_process@1.0.2 actually load? Runtime test results

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

Runtimerequire("child_process")import "child_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 child_process

ES modules (import)

import childProcess from "child_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 childProcess = require("child_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 (1 versions; the newest 1 shown).

VersionsFormatFirst published
1.0.2CommonJSAug 26, 2016

Frequently asked

Is child_process ESM-only?

child_process@1.0.2 is a CommonJS package. child_process ships CommonJS only. require("child_process") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "child_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 child_process with ES module syntax?

Yes. import childProcess from "child_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 child_process work in Bun?

Yes. import "child_process" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does child_process ship TypeScript types?

No. child_process ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity