canirequire › CommonJS › @smithy/config-resolver
Is @smithy/config-resolver ESM-only? Can you require() it?
Last verified Sep 9, 2026 against @smithy/config-resolver@4.7.2. JSON
CommonJS CommonJS — require() works on every Node.js version
@smithy/config-resolver ships CommonJS only. require("@smithy/config-resolver") works everywhere. import "@smithy/config-resolver" 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.
Does @smithy/config-resolver@4.7.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@smithy/config-resolver") from a CommonJS file and import "@smithy/config-resolver" from an ES module.
| Runtime | require("@smithy/config-resolver") | import "@smithy/config-resolver" |
|---|---|---|
| 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/config-resolver
ES modules (import)
import configResolver from "@smithy/config-resolver";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 configResolver = require("@smithy/config-resolver");Module format by version
Derived from the type, main and exports fields of every stable release on npm (111 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 4.0.1 – 4.7.2 | CommonJS | Jan 9, 2025 |
Frequently asked
Is @smithy/config-resolver ESM-only?
@smithy/config-resolver@4.7.2 is a CommonJS package. @smithy/config-resolver ships CommonJS only. require("@smithy/config-resolver") works everywhere. import "@smithy/config-resolver" 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/config-resolver with ES module syntax?
Yes. import configResolver from "@smithy/config-resolver" 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/config-resolver work in Bun?
Yes. import "@smithy/config-resolver" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @smithy/config-resolver ship TypeScript types?
Yes. @smithy/config-resolver 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
- @babel/plugin-transform-parameters 8.0.1ESM-only
- @jest/source-map 30.5.0Dual
- @aws-sdk/client-sso 3.1128.0CommonJS
- @babel/plugin-syntax-object-rest-spread 7.8.3CommonJS
- @babel/plugin-syntax-logical-assignment-operators 7.10.4CommonJS
- @protobufjs/pool 1.1.0CommonJS
- @babel/plugin-syntax-json-strings 7.8.3CommonJS
- @csstools/color-helpers 6.1.1ESM-only