canirequire › CommonJS › @aws-sdk/util-endpoints
Is @aws-sdk/util-endpoints ESM-only? Can you require() it?
Utilities to help with endpoint resolution
Last verified Sep 9, 2026 against @aws-sdk/util-endpoints@3.996.43. JSON
CommonJS CommonJS — require() works on every Node.js version
@aws-sdk/util-endpoints ships CommonJS only. require("@aws-sdk/util-endpoints") works everywhere. import "@aws-sdk/util-endpoints" 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 @aws-sdk/util-endpoints@3.996.43 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@aws-sdk/util-endpoints") from a CommonJS file and import "@aws-sdk/util-endpoints" from an ES module.
| Runtime | require("@aws-sdk/util-endpoints") | import "@aws-sdk/util-endpoints" |
|---|---|---|
| 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 @aws-sdk/util-endpoints
ES modules (import)
import utilEndpoints from "@aws-sdk/util-endpoints";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 utilEndpoints = require("@aws-sdk/util-endpoints");Module format by version
Derived from the type, main and exports fields of every stable release on npm (228 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 3.980.0 – 3.996.43 | CommonJS | Jan 30, 2026 |
Frequently asked
Is @aws-sdk/util-endpoints ESM-only?
@aws-sdk/util-endpoints@3.996.43 is a CommonJS package. @aws-sdk/util-endpoints ships CommonJS only. require("@aws-sdk/util-endpoints") works everywhere. import "@aws-sdk/util-endpoints" 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 @aws-sdk/util-endpoints with ES module syntax?
Yes. import utilEndpoints from "@aws-sdk/util-endpoints" 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 @aws-sdk/util-endpoints work in Bun?
Yes. import "@aws-sdk/util-endpoints" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does @aws-sdk/util-endpoints ship TypeScript types?
Yes. @aws-sdk/util-endpoints 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-id 1.1.4Dual
- @alloc/quick-lru 5.3.0CommonJS
- @babel/helper-annotate-as-pure 8.0.0ESM-only
- @nodelib/fs.walk 3.0.1CommonJS
- @radix-ui/react-use-callback-ref 1.1.4Dual
- @vitest/snapshot 5.0.0ESM-only
- @aws-sdk/credential-provider-env 3.972.70CommonJS
- @sinonjs/fake-timers 15.4.0CommonJS