canirequire › CommonJS › enquirer
Is enquirer ESM-only? Can you require() it?
Stylish, intuitive and user-friendly prompt system. Fast and lightweight enough for small projects, powerful and extensible enough for the most advanced use cases.
Last verified Sep 9, 2026 against enquirer@2.4.1. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
enquirer ships CommonJS only. require("enquirer") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.6. import "enquirer" 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("enquirer") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.6.
- From ES modules use the default import: import enquirer from "enquirer"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does enquirer@2.4.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("enquirer") from a CommonJS file and import "enquirer" from an ES module.
| Runtime | require("enquirer") | import "enquirer" |
|---|---|---|
| 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 enquirer
ES modules (import)
import enquirer from "enquirer";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 enquirer = require("enquirer");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 (37 versions; the newest 37 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 2.4.1 | CommonJS | Aug 21, 2016 |
Frequently asked
Is enquirer ESM-only?
enquirer@2.4.1 is a CommonJS package. enquirer ships CommonJS only. require("enquirer") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.6. import "enquirer" 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 enquirer with ES module syntax?
Yes. import enquirer from "enquirer" 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 enquirer work in Bun?
Yes. import "enquirer" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does enquirer ship TypeScript types?
Yes. enquirer 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
- @smithy/util-endpoints 3.7.2CommonJS
- @smithy/node-config-provider 4.6.2CommonJS
- @smithy/util-body-length-browser 4.5.2CommonJS
- co 4.6.0CommonJS
- xml2js 0.6.2CommonJS
- @aws-sdk/region-config-resolver 3.972.48CommonJS
- big.js 7.0.1Dual
- @swc/core 1.16.2CommonJS