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

> yallist@5.0.0 ships CommonJS and ESM builds. Dual package — require() works on every Node.js version we test; import works too.

Yet Another Linked List

Last verified Sep 9, 2026 against yallist@5.0.0.

yallist publishes both a CommonJS entry and a native ESM entry (ESM added in 5.0.0). require("yallist") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "yallist" works alongside it.

## What to do

1. Nothing to change. require("yallist") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import * as yallist from "yallist" works alongside it; use named imports for what the ESM entry exports.
2. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 5.0.0 (Apr 9, 2024)
- Module format: Dual (CommonJS + ESM)
- Last CommonJS version: 5.0.0
- Native ESM since: 5.0.0
- TypeScript types: bundled
- Node engines: >=18
- Weekly downloads: 277.0M
- License: BlueOak-1.0.0

## Runtime test results for yallist@5.0.0

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

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

ES modules:

```js
import * as yallist from "yallist";
```

Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.

CommonJS:

```js
const yallist = require("yallist");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 5.0.0 | Dual (CommonJS + ESM) | Apr 9, 2024 |
| 1.0.0 – 4.0.0 | CommonJS | Dec 18, 2015 |

## Frequently asked

**Is yallist ESM-only?**

yallist@5.0.0 ships CommonJS and ESM builds. yallist publishes both a CommonJS entry and a native ESM entry (ESM added in 5.0.0). require("yallist") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18. import "yallist" works alongside it.

**Can I require yallist?**

Yes. yallist ships a CommonJS entry alongside the native ESM entry. require("yallist") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=18.

**Does yallist work in Bun?**

Yes. import "yallist" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does yallist ship TypeScript types?**

Yes. yallist bundles its own type declarations; no @types package is needed.

## Links

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