For those using [ `@next/eslint-plugin-next`](https://nextjs.org/docs/app/building-your-application/configuring/eslint#migrating-existing-config), the [ESLint Compatibility Utilities](https://eslint.org/blog/2024/05/eslint-compatibility-utilities/) worked for me. CodeSandbox example: https://codesandbox.io/p/devbox/vibrant-hill-29h4tw

          For those using [ `@next/eslint-plugin-next`](https://nextjs.org/docs/app/building-your-application/configuring/eslint#migrating-existing-config), the [ESLint Compatibility Utilities](https://eslint.org/blog/2024/05/eslint-compatibility-utilities/) worked for me. CodeSandbox example: https://codesandbox.io/p/devbox/vibrant-hill-29h4tw

npm install --save-dev @next/eslint-plugin-next @eslint/compat @eslint/eslintrc

eslint.config.mjs:

import { fixupConfigRules } from "@eslint/compat";
import { FlatCompat } from "@eslint/eslintrc";

const compat = new FlatCompat();

export default [
  {
    ignores: [".next/"],
  },
  ...fixupConfigRules(compat.extends("plugin:@next/next/core-web-vitals")),
];

package.json:

{
  "scripts": {
    "lint": "eslint"
  },
  "dependencies": {
    "next": "^14.2.3",
    "react": "^18",
    "react-dom": "^18"
  },
  "devDependencies": {
    "@eslint/compat": "^1.0.1",
    "@eslint/eslintrc": "^3.0.2",
    "@next/eslint-plugin-next": "^14.2.3",
    "eslint": "^9.2.0"
  }
}

Originally posted by @saltycrane in https://github.com/vercel/next.js/issues/64409#issuecomment-2113690940

luke-hanwook / every-troubleshooting