# Is dotenv-expand ESM-only? Can you require() it?

> dotenv-expand@1000.0.0 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Expand environment variables using dotenv

Last verified Sep 9, 2026 against dotenv-expand@1000.0.0.

dotenv-expand ships CommonJS only. require("dotenv-expand") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=16. import "dotenv-expand" 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.

## What to do

1. require("dotenv-expand") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=16.
2. From ES modules use the default import: import dotenvExpand from "dotenv-expand"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 1000.0.0 (Jul 29, 2026)
- Module format: CommonJS
- Last CommonJS version: 1000.0.0
- TypeScript types: bundled
- Node engines: >=16
- Weekly downloads: 36.7M
- License: BSD-3-Clause

## Runtime test results for dotenv-expand@1000.0.0

Installed and executed on Sep 9, 2026 with require("dotenv-expand") from a CommonJS file and import "dotenv-expand" from an ES module.

| Runtime | require("dotenv-expand") | import "dotenv-expand" |
|---|---|---|
| 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 dotenv-expand

ES modules:

```js
import dotenvExpand from "dotenv-expand";
```

CommonJS:

```js
const dotenvExpand = require("dotenv-expand");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (30 versions; the newest 30 shown).

| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 1000.0.0 | CommonJS | Jan 21, 2016 |

## Frequently asked

**Is dotenv-expand ESM-only?**

dotenv-expand@1000.0.0 is a CommonJS package. dotenv-expand ships CommonJS only. require("dotenv-expand") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=16. import "dotenv-expand" 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 dotenv-expand with ES module syntax?**

Yes. import dotenvExpand from "dotenv-expand" 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 dotenv-expand work in Bun?**

Yes. import "dotenv-expand" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does dotenv-expand ship TypeScript types?**

Yes. dotenv-expand bundles its own type declarations; no @types package is needed.

## Links

- [dotenv-expand on npm](https://www.npmjs.com/package/dotenv-expand)
- [Source repository](https://github.com/dotenvx/dotenv-expand)
- [HTML version](https://canirequire.com/package/dotenv-expand/)
- [JSON version](https://canirequire.com/package/dotenv-expand.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.