{
  "id": 2565653,
  "title": "eslint-plugin-jsx-a11y says it doesn't support ESLint 10. It does.",
  "url": "https://urgent.news/2026/08/22/eslint-plugin-jsx-a11y-says-it-doesnt-support-eslint-10-it-does",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-22T11:01:37.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/booyaka101/eslint-plugin-jsx-a11y-says-it-doesnt-support-eslint-10-it-does-380f"
  },
  "original_language": "en",
  "account": "eslint-plugin-jsx-a11y has stated that it does not support ESLint 10, but this is incorrect. The plugin functions properly with ESLint 10. The issue lies within the peerDependencies specified in the plugin's manifest, which does not accurately reflect its compatibility with newer versions of ESLint. When using the --legacy-peer-deps flag and enabling all rules, the plugin works seamlessly with ESLint 10. This discrepancy highlights the importance of understanding peer dependencies and their relationship with ESLint versions.",
  "summary": "eslint-plugin-jsx-a11y@6.10.2 declares this: \"peerDependencies\" : { \"eslint\" : \"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9\" } ESLint's current release is 10.9.0, so npm refuses to put them in the same tree: npm error Could not resolve dependency: npm error peer eslint@\"^3 || ... || ^9\" from eslint-plugin-jsx-a11y@6.10.2 I forced it with --legacy-peer-deps , turned on all 39 rules the plugin exports,…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}