canirequire

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. Markdown · JSON

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

@smithy/config-resolver ships CommonJS only. require("@smithy/config-resolver") 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/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.

What to do

  1. require("@smithy/config-resolver") 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 configResolver from "@smithy/config-resolver"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
4.7.2 (Aug 15, 2026)
Module format
CommonJS
Last CommonJS version
4.7.2
TypeScript types
Bundled
Node engines
>=18.0.0
Weekly downloads
27.8M
License
Apache-2.0

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.

Runtimerequire("@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.0✓ 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, corrected where a runtime test of that version contradicted them (111 versions; the newest 60 shown).

VersionsFormatFirst published
4.0.1 – 4.7.2CommonJSJan 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 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/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.0 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

Similar popularity