"The most consequential change in v10 is the complete removal of the legacy eslintrc configuration system. Since v9, flat config (eslint.config.js) has been the default, but the old format was still accessible via LegacyESLint."
"Teams still on .eslintrc files will need to migrate before upgrading. The official migration tool makes the transition straightforward: npx @eslint/migrate-config .eslintrc.json."
"Alongside the config cleanup, v10 changes how ESLint locates its configuration file. Rather than searching from the current working directory, it now starts from the directory of each linted file."
"JSX reference tracking is another headline addition. Previously, ESLint did not recognise JSX identifiers as variable references, producing false positives with rules like no-unused-vars."
ESLint version 10 marks a significant update by removing the legacy eslintrc configuration system and finalizing years of architectural improvements. The flat config system is now the only option, requiring teams to migrate from .eslintrc files. The release also changes how ESLint locates configuration files, improving functionality for monorepo setups. Additionally, JSX reference tracking has been added to prevent false positives in variable usage, enhancing the overall developer experience and addressing common issues faced by users.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]