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

> next@16.3.4 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

The React Framework

Last verified Sep 9, 2026 against next@16.3.4.

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

## Facts

- Latest: 16.3.4 (Aug 31, 2026)
- Module format: CommonJS
- Last CommonJS version: 16.3.4
- TypeScript types: bundled
- Node engines: >=20.9.0
- Weekly downloads: 40.6M
- License: MIT

## Runtime test results for next@16.3.4

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

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

ES modules:

```js
import next from "next";
```

CommonJS:

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

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 15.5.3 – 16.3.4 | CommonJS | Sep 10, 2025 |

## Frequently asked

**Is next ESM-only?**

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

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

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

**Does next ship TypeScript types?**

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

## Links

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