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

> @smithy/node-config-provider@4.6.2 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Load config default values from ini config files and environmental variable

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

@smithy/node-config-provider ships CommonJS only. require("@smithy/node-config-provider") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.0.0. 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.

## What to do

1. require("@smithy/node-config-provider") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.0.0.
2. From ES modules use the default import: import nodeConfigProvider from "@smithy/node-config-provider"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 4.6.2 (Aug 15, 2026)
- Module format: CommonJS
- Last CommonJS version: 4.6.2
- TypeScript types: bundled
- Node engines: >=18.0.0
- Weekly downloads: 31.3M
- License: Apache-2.0

## Runtime test results for @smithy/node-config-provider@4.6.2

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.

| Runtime | require("@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.0 | works | works |

## How to import @smithy/node-config-provider

ES modules:

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

CommonJS:

```js
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).

| Versions | Format | First published |
|---|---|---|
| 3.1.7 – 4.6.2 | CommonJS | Sep 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 on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.0.0. 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.0 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

- [@smithy/node-config-provider on npm](https://www.npmjs.com/package/@smithy/node-config-provider)
- [Source repository](https://github.com/smithy-lang/smithy-typescript)
- [HTML version](https://canirequire.com/package/@smithy/node-config-provider/)
- [JSON version](https://canirequire.com/package/@smithy/node-config-provider.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.