# Is for-each ESM-only? Can you require() it?

> for-each@0.3.5 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

A better forEach

Last verified Sep 9, 2026 against for-each@0.3.5.

for-each ships CommonJS only. require("for-each") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "for-each" 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("for-each") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4.
2. From ES modules use the default import: import forEach from "for-each"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 0.3.5 (Feb 11, 2025)
- Module format: CommonJS
- Last CommonJS version: 0.3.5
- TypeScript types: bundled
- Node engines: >= 0.4
- Weekly downloads: 72.7M
- License: MIT

## Runtime test results for for-each@0.3.5

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

| Runtime | require("for-each") | import "for-each" |
|---|---|---|
| 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 for-each

ES modules:

```js
import forEach from "for-each";
```

CommonJS:

```js
const forEach = require("for-each");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 0.3.5 | CommonJS | Sep 29, 2012 |

## Frequently asked

**Is for-each ESM-only?**

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

Yes. import forEach from "for-each" 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 for-each work in Bun?**

Yes. import "for-each" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does for-each ship TypeScript types?**

Yes. for-each bundles its own type declarations; no @types package is needed.

## Links

- [for-each on npm](https://www.npmjs.com/package/for-each)
- [Source repository](https://github.com/Raynos/for-each)
- [HTML version](https://canirequire.com/package/for-each/)
- [JSON version](https://canirequire.com/package/for-each.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.