canirequire › No JS entry point › 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. JSON
No JS entry point No JavaScript entry point
eslint-config-next does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
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.
| Runtime | require("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 | ✗ failserror: 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' | ✗ failserror: 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' |
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";CommonJS (require)
Not applicable.
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 has no importable main entry. eslint-config-next does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
Does eslint-config-next work in Bun?
Importing eslint-config-next failed in Bun 1.4 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 no js entry point packages
- type-fest 5.9.0No entry
- storybook 10.6.0No entry
- @storybook/addon-docs 10.6.0No entry
- @storybook/addon-a11y 10.6.0No entry
- eslint-plugin-storybook 10.6.0No entry
- tsup 8.5.1No entry
- typedoc 0.28.20No entry
- normalize.css 8.0.1No entry
Similar popularity
- react-router-dom 7.18.3Dual
- read-cache 1.0.2CommonJS
- thenify-all 1.6.0CommonJS
- preact 10.29.8Dual
- classnames 2.5.1CommonJS
- node-int64 0.4.0CommonJS
- handlebars 4.7.9CommonJS
- reflect-metadata 0.2.2CommonJS