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

> unplugin@3.3.0 is ESM-only. ESM-only since 3.0.0 — last CommonJS version is 2.3.11.

Unified plugin system for build tools

Last verified Sep 9, 2026 against unplugin@3.3.0.

unplugin dropped its CommonJS build in 3.0.0 (January 2026). The last version with a plain require()-able CommonJS entry is 2.3.11, published Nov 22, 2025; it declares support for Node.js >=18.12.0.

On Node.js 20.19+, 22.12+ and newer, require("unplugin") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Node.js 18 has no require(esm), and unplugin@3.3.0 declares Node.js ^20.19.0 || >=22.12.0, so 18 is outside its supported range anyway.

unplugin@3.3.0 declares engines "^20.19.0 || >=22.12.0", so Node.js 18 is outside its supported range regardless of module format.

## What to do

1. On Node.js 20.19+, 22.12+ and newer, require("unplugin") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26.
2. From a CommonJS file, use a dynamic import inside an async function: const unplugin = await import("unplugin"). That works on every Node.js version the package supports (^20.19.0 || >=22.12.0).
3. If you need a synchronous require() or run Node.js 18: npm install unplugin@2.3.11, the last CommonJS release (published Nov 22, 2025); it declares Node.js >=18.12.0.
4. unplugin@3.3.0 declares engines "^20.19.0 || >=22.12.0", so Node.js 18 is unsupported regardless: upgrade Node.js or pin an older release.
5. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 3.3.0 (Jun 29, 2026)
- Module format: ESM-only
- Last CommonJS version: 2.3.11
- ESM-only since: 3.0.0 (Jan 22, 2026)
- TypeScript types: bundled
- Node engines: ^20.19.0 || >=22.12.0
- Weekly downloads: 51.6M
- License: MIT

## Runtime test results for unplugin@3.3.0

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

| Runtime | require("unplugin") | import "unplugin" |
|---|---|---|
| Node.js 18 | fails (ERR_REQUIRE_ESM) | fails (ERR_INVALID_ARG_TYPE) |
| 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 unplugin

ES modules:

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

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

CommonJS:

```js
// Node.js 20.19+, 22.12+ and newer (verified):
const unplugin = require("unplugin");

// Any Node.js version the package supports (^20.19.0 || >=22.12.0), from an async function:
async function main() {
  const unplugin = await import("unplugin");
}

// Or pin the last CommonJS release (declares Node.js >=18.12.0):
// npm install unplugin@2.3.11
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 3.0.0 – 3.3.0 | ESM-only | Jan 22, 2026 |
| 0.9.6 – 2.3.11 | Dual (CommonJS + ESM) | Sep 21, 2022 |

## Frequently asked

**Is unplugin ESM-only?**

unplugin@3.3.0 is ESM-only. unplugin dropped its CommonJS build in 3.0.0 (January 2026). The last version with a plain require()-able CommonJS entry is 2.3.11, published Nov 22, 2025; it declares support for Node.js >=18.12.0.

**Which version of unplugin still supports CommonJS / require()?**

2.3.11 is the last version of unplugin with a CommonJS build; it declares Node.js >=18.12.0. Install it with "npm install unplugin@2.3.11". Every version from 3.0.0 on is ESM-only.

**How do I use unplugin from a CommonJS file?**

From a CommonJS file, use a dynamic import inside an async function: const unplugin = await import("unplugin"). That works on every Node.js version the package supports (^20.19.0 || >=22.12.0). On Node.js 20.19+, 22.12+ and newer, require("unplugin") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Alternatively pin unplugin@2.3.11 (declares Node.js >=18.12.0).

**Does unplugin work in Bun?**

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

**Does unplugin ship TypeScript types?**

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

## Links

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