canirequire › CommonJS › @smithy/credential-provider-imds
Is @smithy/credential-provider-imds ESM-only? Can you require() it?
AWS credential provider that sources credentials from the EC2 instance metadata service and ECS container metadata service
Last verified Sep 9, 2026 against @smithy/credential-provider-imds@4.5.2. JSON
CommonJS CommonJS — require() works on every Node.js version
@smithy/credential-provider-imds ships CommonJS only. require("@smithy/credential-provider-imds") works everywhere. import "@smithy/credential-provider-imds" 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/credential-provider-imds@4.5.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@smithy/credential-provider-imds") from a CommonJS file and import "@smithy/credential-provider-imds" from an ES module.
| Runtime | require("@smithy/credential-provider-imds") | import "@smithy/credential-provider-imds" |
|---|---|---|
| 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/credential-provider-imds
ES modules (import)
import credentialProviderImds from "@smithy/credential-provider-imds";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 credentialProviderImds = require("@smithy/credential-provider-imds");Module format by version
Derived from the type, main and exports fields of every stable release on npm (109 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 3.2.5 – 4.5.2 | CommonJS | Oct 21, 2024 |
Frequently asked
Is @smithy/credential-provider-imds ESM-only?
@smithy/credential-provider-imds@4.5.2 is a CommonJS package. @smithy/credential-provider-imds ships CommonJS only. require("@smithy/credential-provider-imds") works everywhere. import "@smithy/credential-provider-imds" 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/credential-provider-imds with ES module syntax?
Yes. import credentialProviderImds from "@smithy/credential-provider-imds" 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/credential-provider-imds work in Bun?
Yes. import "@smithy/credential-provider-imds" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @smithy/credential-provider-imds ship TypeScript types?
Yes. @smithy/credential-provider-imds 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
- @smithy/core 3.33.3Dual
- @protobufjs/inquire 1.1.2CommonJS
- @babel/plugin-transform-modules-commonjs 8.0.1ESM-only
- @smithy/util-base64 4.6.2CommonJS
- @smithy/middleware-serde 4.5.2CommonJS
- @aws-sdk/nested-clients 3.997.44Dual
- @smithy/url-parser 4.5.2CommonJS
- @noble/hashes 2.4.0ESM-only