canirequire

canirequire › CommonJS › eslint-config-next

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

ESLint configuration used by Next.js.

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

CommonJS CommonJS on paper — require() failed in our runtime test

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.
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

Does eslint-config-next@16.3.4 actually load? Runtime test results

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.

Runtimerequire("eslint-config-next")import "eslint-config-next"
Node.js 18✗ failsMODULE_NOT_FOUND✗ failsMODULE_NOT_FOUND
Node.js 20✗ failsMODULE_NOT_FOUND✗ failsMODULE_NOT_FOUND
Node.js 22✗ failsMODULE_NOT_FOUND✗ failsMODULE_NOT_FOUND
Node.js 24✗ failsMODULE_NOT_FOUND✗ failsMODULE_NOT_FOUND
Node.js 26✗ failsMODULE_NOT_FOUND✗ failsMODULE_NOT_FOUND
Bun 1.4.0✗ failsError✗ failsError

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import eslint-config-next

ES modules (import)

import eslintConfigNext from "eslint-config-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)

// 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, corrected where a runtime test of that version contradicted them (281 versions; the newest 60 shown).

VersionsFormatFirst published
15.5.3 – 16.3.4CommonJSSep 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

Other commonjs packages

Similar popularity