canirequire

canirequire › CommonJS › @aws-sdk/credential-provider-env

Is @aws-sdk/credential-provider-env ESM-only? Can you require() it?

AWS credential provider that sources credentials from known environment variables

Last verified Sep 9, 2026 against @aws-sdk/credential-provider-env@3.972.70. Markdown · JSON

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

@aws-sdk/credential-provider-env ships CommonJS only. require("@aws-sdk/credential-provider-env") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=20.0.0. import "@aws-sdk/credential-provider-env" 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("@aws-sdk/credential-provider-env") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=20.0.0.
  2. From ES modules use the default import: import credentialProviderEnv from "@aws-sdk/credential-provider-env"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
3.972.70 (Aug 21, 2026)
Module format
CommonJS
Last CommonJS version
3.972.70
TypeScript types
Bundled
Node engines
>=20.0.0
Weekly downloads
59.0M
License
Apache-2.0

Does @aws-sdk/credential-provider-env@3.972.70 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("@aws-sdk/credential-provider-env") from a CommonJS file and import "@aws-sdk/credential-provider-env" from an ES module.

Runtimerequire("@aws-sdk/credential-provider-env")import "@aws-sdk/credential-provider-env"
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 @aws-sdk/credential-provider-env

ES modules (import)

import credentialProviderEnv from "@aws-sdk/credential-provider-env";

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 credentialProviderEnv = require("@aws-sdk/credential-provider-env");

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 (297 versions; the newest 60 shown).

VersionsFormatFirst published
3.972.11 – 3.972.70CommonJSFeb 24, 2026

Frequently asked

Is @aws-sdk/credential-provider-env ESM-only?

@aws-sdk/credential-provider-env@3.972.70 is a CommonJS package. @aws-sdk/credential-provider-env ships CommonJS only. require("@aws-sdk/credential-provider-env") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=20.0.0. import "@aws-sdk/credential-provider-env" 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/credential-provider-env with ES module syntax?

Yes. import credentialProviderEnv from "@aws-sdk/credential-provider-env" 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/credential-provider-env work in Bun?

Yes. import "@aws-sdk/credential-provider-env" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does @aws-sdk/credential-provider-env ship TypeScript types?

Yes. @aws-sdk/credential-provider-env bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity