canirequire › CommonJS › @smithy/smithy-client
Is @smithy/smithy-client ESM-only? Can you require() it?
Last verified Sep 9, 2026 against @smithy/smithy-client@4.15.2. JSON
CommonJS CommonJS — require() works on every Node.js version
@smithy/smithy-client ships CommonJS only. require("@smithy/smithy-client") works everywhere. import "@smithy/smithy-client" 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/smithy-client@4.15.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@smithy/smithy-client") from a CommonJS file and import "@smithy/smithy-client" from an ES module.
| Runtime | require("@smithy/smithy-client") | import "@smithy/smithy-client" |
|---|---|---|
| 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/smithy-client
ES modules (import)
import smithyClient from "@smithy/smithy-client";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 smithyClient = require("@smithy/smithy-client");Module format by version
Derived from the type, main and exports fields of every stable release on npm (194 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 4.10.4 – 4.15.2 | CommonJS | Jan 9, 2026 |
Frequently asked
Is @smithy/smithy-client ESM-only?
@smithy/smithy-client@4.15.2 is a CommonJS package. @smithy/smithy-client ships CommonJS only. require("@smithy/smithy-client") works everywhere. import "@smithy/smithy-client" 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/smithy-client with ES module syntax?
Yes. import smithyClient from "@smithy/smithy-client" 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/smithy-client work in Bun?
Yes. import "@smithy/smithy-client" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @smithy/smithy-client ship TypeScript types?
Yes. @smithy/smithy-client 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
- @radix-ui/react-dialog 1.1.23Dual
- @smithy/querystring-builder 4.5.2CommonJS
- @tailwindcss/oxide-linux-x64-musl 4.3.3CommonJS
- @aws-sdk/xml-builder 3.972.40CommonJS
- @sinonjs/commons 4.0.0-alpha.0Dual
- @rollup/pluginutils 5.4.0Dual
- @napi-rs/wasm-runtime 1.2.3Dual
- @openai/codex 0.153.4ESM-only