canirequire

canirequire › CommonJS › @oclif/config

Is @oclif/config ESM-only? Can you require() it?

base config object and standard interfaces for oclif components

Last verified Sep 9, 2026 against @oclif/config@1.18.17. Markdown · JSON

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

@oclif/config ships CommonJS only. require("@oclif/config") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.0.0. import "@oclif/config" 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("@oclif/config") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.0.0.
  2. From ES modules use the default import: import config from "@oclif/config"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
  4. This package is deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Latest
1.18.17 (Aug 20, 2023)
Module format
CommonJS
Last CommonJS version
1.18.17
TypeScript types
Bundled
Node engines
>=8.0.0
Weekly downloads
2.0M
License
MIT

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

Does @oclif/config@1.18.17 actually load? Runtime test results

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

Runtimerequire("@oclif/config")import "@oclif/config"
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 @oclif/config

ES modules (import)

import config from "@oclif/config";

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 config = require("@oclif/config");

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 (131 versions; the newest 60 shown).

VersionsFormatFirst published
1.6.32 – 1.18.17CommonJSJun 18, 2018

Frequently asked

Is @oclif/config ESM-only?

@oclif/config@1.18.17 is a CommonJS package. @oclif/config ships CommonJS only. require("@oclif/config") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.0.0. import "@oclif/config" 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 @oclif/config with ES module syntax?

Yes. import config from "@oclif/config" 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 @oclif/config work in Bun?

Yes. import "@oclif/config" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does @oclif/config ship TypeScript types?

Yes. @oclif/config bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity