canirequire › CommonJS › next
Is next ESM-only? Can you require() it?
The React Framework
Last verified Sep 9, 2026 against next@16.3.4. JSON
CommonJS CommonJS — require() works on every Node.js version
next ships CommonJS only. require("next") works everywhere. 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.
Does next@16.3.4 actually load? Runtime test results
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 | ✓ works | ✓ works |
How to import next
ES modules (import)
import next from "next";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
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 everywhere. 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 on Sep 9, 2026.
Does next ship TypeScript types?
Yes. next bundles its own type declarations; no @types package is needed.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- is-potential-custom-element-name 1.0.1CommonJS
- uglify-js 3.19.3CommonJS
- any-promise 1.3.0CommonJS
- define-property 2.0.2CommonJS
- tar-fs 3.1.3CommonJS
- array-flatten 3.0.0CommonJS
- @aws-sdk/middleware-host-header 3.972.45CommonJS
- file-type 22.0.2ESM-only