chore: migrate to ESLint 9 with flat config #839
Merged
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.
Summary
This PR migrates from ESLint 8 to ESLint 9 with the new flat config format, enabling the use of
@automattic/eslint-plugin-wpvip1.0.0.Key Changes
@automattic/eslint-plugin-wpvip0.13.1 → ^1.0.0babel-eslint(replaced by@babel/eslint-parserin the plugin)eslint-plugin-flowtype(not used in codebase)eslint-plugin-wpcalypso(functionality now in wpvip plugin).eslintrc.jstoeslint.config.js(flat config).eslintignorecontents intoeslint.config.jswebpack.config.jsto handle paths without leading./Notes
The config uses individual configs (
javascript,testing) instead ofrecommendedto work around a bug in@automattic/eslint-plugin-wpvip@1.0.0where the react-hooks config uses the legacy plugins array format instead of flat config object format.Related
This enables closing Dependabot PR #838 which was blocked by ESLint peer dependency conflicts.
Test plan
npm run lint-jspassesnpm run buildsucceeds🤖 Generated with Claude Code