node -e "import {configs} from '@next/eslint-plugin-next';" file:///home/tobias/code/repro-eslint-mcp-jiti/[eval1]:1 import {configs} from '@next/eslint-plugin-next'; ^^^^^^^ SyntaxError: Named export 'configs' not found. The requested module '@next/eslint-plugin-next' is a CommonJS module, which may not support all module.exports as named exports. CommonJS modules can always be imported via the default export, for example using:

import pkg from '@next/eslint-plugin-next'; const {configs} = pkg;

at #_instantiate (node:internal/modules/esm/module_job:254:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:369:5)
at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:278:26)
at async ModuleLoader.executeModuleJob (node:internal/modules/esm/loader:275:20)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5)

Node.js v24.11.0

TL;DR

The issue can be fixed by changing how @next/eslint-plugin-next defines its named exports, specifically by using a data property instead of a getter for configs.

Guidance

• The error occurs because Node.js ignores top-level getters for synthetic named exports when importing CommonJS (CJS) modules as ES modules (ESM).
• To fix this, the @next/eslint-plugin-next package should define configs as a data property on the exports object instead of using Object.defineProperty with a getter.
• As a temporary workaround, you can import the entire package and access configs from it, like this: import pkg from '@next/eslint-plugin-next'; const { configs } = pkg;.
• Verify the fix by running the same command that previously produced the error: node -e "import {configs} from '@next/eslint-plugin-next';".

Example

// Instead of top-level getter:
Object.defineProperty(exports, "configs", {
  enumerable: true,
  value: configs  // <- data property, not a getter
});

Notes

This fix assumes that the issue is indeed caused by the way @next/eslint-plugin-next defines its named exports. If the issue persists after applying this fix, further investigation may be needed.

Recommendation

Apply the workaround by importing the entire package and accessing configs from it, as this is a more immediate solution that does not require modifying the @next/eslint-plugin-next package directly.