canirequire › CommonJS › cosmiconfig
Is cosmiconfig ESM-only? Can you require() it?
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
Last verified Sep 9, 2026 against cosmiconfig@10.0.1. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
cosmiconfig ships CommonJS only. require("cosmiconfig") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.18 || >= 24. import "cosmiconfig" 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("cosmiconfig") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.18 || >= 24.
- From ES modules use the default import: import cosmiconfig from "cosmiconfig"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does cosmiconfig@10.0.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("cosmiconfig") from a CommonJS file and import "cosmiconfig" from an ES module.
| Runtime | require("cosmiconfig") | import "cosmiconfig" |
|---|---|---|
| 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 cosmiconfig
ES modules (import)
import cosmiconfig from "cosmiconfig";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 cosmiconfig = require("cosmiconfig");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 (56 versions; the newest 56 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 10.0.1 | CommonJS | Nov 12, 2015 |
Frequently asked
Is cosmiconfig ESM-only?
cosmiconfig@10.0.1 is a CommonJS package. cosmiconfig ships CommonJS only. require("cosmiconfig") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^22.18 || >= 24. import "cosmiconfig" 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 cosmiconfig with ES module syntax?
Yes. import cosmiconfig from "cosmiconfig" 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 cosmiconfig work in Bun?
Yes. import "cosmiconfig" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does cosmiconfig ship TypeScript types?
Yes. cosmiconfig 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
- jose 6.2.12ESM-only
- ajv-formats 3.0.1CommonJS
- @vitest/pretty-format 5.0.0ESM-only
- espree 11.2.0Dual
- lightningcss-linux-x64-gnu 1.33.0CommonJS
- strip-final-newline 4.0.0ESM-only
- prettier 3.9.6Dual
- @opentelemetry/api-logs 0.222.0CommonJS