canirequire

canirequire › CommonJS › @smithy/node-config-provider

Is @smithy/node-config-provider ESM-only? Can you require() it?

Load config default values from ini config files and environmental variable

Last verified Sep 9, 2026 against @smithy/node-config-provider@4.6.2. JSON

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

@smithy/node-config-provider ships CommonJS only. require("@smithy/node-config-provider") works everywhere. import "@smithy/node-config-provider" 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.

It also declares a "module" field, so bundlers such as webpack, Vite and esbuild pick up an ESM build for tree-shaking.

Latest
4.6.2 (Aug 15, 2026)
Module format
CommonJS
Last CommonJS version
4.6.2
TypeScript types
Bundled
Node engines
>=18.0.0
License
Apache-2.0

Does @smithy/node-config-provider@4.6.2 actually load? Runtime test results

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

Runtimerequire("@smithy/node-config-provider")import "@smithy/node-config-provider"
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✓ works✓ works

How to import @smithy/node-config-provider

ES modules (import)

import nodeConfigProvider from "@smithy/node-config-provider";

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 nodeConfigProvider = require("@smithy/node-config-provider");

Module format by version

Derived from the type, main and exports fields of every stable release on npm (105 versions; the newest 60 shown).

VersionsFormatFirst published
3.1.7 – 4.6.2CommonJSSep 13, 2024

Frequently asked

Is @smithy/node-config-provider ESM-only?

@smithy/node-config-provider@4.6.2 is a CommonJS package. @smithy/node-config-provider ships CommonJS only. require("@smithy/node-config-provider") works everywhere. import "@smithy/node-config-provider" 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 @smithy/node-config-provider with ES module syntax?

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

Yes. import "@smithy/node-config-provider" loaded successfully in Bun 1.4 on Sep 9, 2026.

Does @smithy/node-config-provider ship TypeScript types?

Yes. @smithy/node-config-provider bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity