Fix ESLint 9 and Next.js 16 compatibility issues #130
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eslint-config-next@16.0.10requires ESLint 9, but the project was on ESLint 8, causing peer dependency conflicts duringnpm install.Changes
Upgraded to ESLint 9 ecosystem:
eslint: ^8 → ^9@typescript-eslint/eslint-plugin,@typescript-eslint/parser: ^7.2.0 → ^8.0.0eslint-plugin-react-hooks: ^4.6.2 → ^5.0.0Upgraded Next.js to match eslint-config-next version:
next: 14.2.4 → 16.0.10Migrated to ESLint 9 flat config:
.eslintrc.ymlwitheslint.config.mjsnext linttoeslint .(Next.js 16 removed the lint command)Build configuration:
--webpackflag to build script (Next.js 16 defaults to Turbopack; project requires webpack for existing config)ts-nodedev dependency for Jest config✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.