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

> eslint-config-next@16.3.4 declares a CommonJS entry, but require() fails at runtime. CommonJS on paper — require() failed in our runtime test.

ESLint configuration used by Next.js.

Last verified Sep 9, 2026 against eslint-config-next@16.3.4.

eslint-config-next declares a CommonJS entry only, but require("eslint-config-next") failed on every Node.js version in our probe: Cannot find module 'next/dist/compiled/babel/eslint-parser'. import "eslint-config-next" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

## What to do

1. require("eslint-config-next") failed in our probe on every Node.js version (Cannot find module 'next/dist/compiled/babel/eslint-parser'); check the package README for peer dependencies or setup before relying on it.
2. From ES modules use the default import: import eslintConfigNext from "eslint-config-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: not declared
- Weekly downloads: 29.2M
- License: MIT

## Runtime test results for eslint-config-next@16.3.4

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

| Runtime | require("eslint-config-next") | import "eslint-config-next" |
|---|---|---|
| Node.js 18 | fails (MODULE_NOT_FOUND) | fails (MODULE_NOT_FOUND) |
| Node.js 20 | fails (MODULE_NOT_FOUND) | fails (MODULE_NOT_FOUND) |
| Node.js 22 | fails (MODULE_NOT_FOUND) | fails (MODULE_NOT_FOUND) |
| Node.js 24 | fails (MODULE_NOT_FOUND) | fails (MODULE_NOT_FOUND) |
| Node.js 26 | fails (MODULE_NOT_FOUND) | fails (MODULE_NOT_FOUND) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import eslint-config-next

ES modules:

```js
import eslintConfigNext from "eslint-config-next";
```

CommonJS:

```js
// require("eslint-config-next") failed in our probe on every Node.js version we test (Cannot find module 'next/dist/compiled/babel/eslint-parser'); see the runtime table.
const eslintConfigNext = require("eslint-config-next");
```

## Module format by version

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

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

## Frequently asked

**Is eslint-config-next ESM-only?**

eslint-config-next@16.3.4 declares a CommonJS entry, but require() fails at runtime. eslint-config-next declares a CommonJS entry only, but require("eslint-config-next") failed on every Node.js version in our probe: Cannot find module 'next/dist/compiled/babel/eslint-parser'. import "eslint-config-next" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

**Can I require eslint-config-next?**

Not in practice. eslint-config-next declares a CommonJS entry, but require("eslint-config-next") failed on every Node.js version in our probe: Cannot find module 'next/dist/compiled/babel/eslint-parser'. Check the package README for peer dependencies or setup before relying on it.

**Can I import eslint-config-next with ES module syntax?**

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

Importing eslint-config-next failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module 'next/dist/compiled/babel/eslint-parser' from '/Users/boat/Projects/top-seo/data/probe-work/eslint-config-next/node_modules/eslint-config-next/dist/parser.js'

**Does eslint-config-next ship TypeScript types?**

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

## Links

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