ESLint 10.0.0 has been officially released, introducing a series of significant changes that will impact both current and future development practices. Key among these changes is the complete removal of the traditional eslintrc configuration files, with flat configuration now being the sole option. This shift aims to enhance configuration resolution, especially for monorepo projects, by utilizing a new algorithm that begins its search from the directory of each file being linted.
Support for older Node.js versions has also been discontinued, with ESLint v10.0.0 requiring a minimum of Node.js v20.19.0. This release comes with several notable enhancements, such as improved JSX reference tracking which refines scope analysis in React projects, and the introduction of built-in TypeScript definitions for Espree and ESLint Scope.
Rule testing sees advancements with the RuleTester now offering assertion options and improved error location reporting. Additionally, a new countThis option has been added to the max-params rule to further customize parameter checks.
The migration to this new version is mandatory; legacy patterns, including .eslintrc files, .eslintignore, and eslint-env comments, have been officially deprecated without any opt-out option. This update also removes certain deprecated context members and SourceCode methods, and modifies the Program AST node range to encompass the entire source text. Furthermore, jiti version 2.2.0 or higher is now required for TypeScript config files.
Overall, ESLint 10.0.0 presents a comprehensive overhaul designed to streamline configuration practices and enhance language support, setting new standards for modern JavaScript and TypeScript development.

Collections

ESLint 10.0.0 mandates flat configuration files, removing support for legacy eslintrc formats entirely. The release requires Node.js v20.19.0+, adds built-in TypeScript definitions for Espree and ESLint Scope, improves JSX reference tracking for React projects, and enhances RuleTester with assertion options. Migration is mandatory with no opt-out for deprecated patterns including .eslintrc, .eslintignore, and eslint-env comments.

ESLint 10.0.0: A New Era of Configuration and Language Support

Eslint is dead-end. Biome is the future

Just use oxfmt instead, it’s way faster and more beautiful

At this point I just care about jQuery 4 :)

This is still the only reasonable linter, Biome is pointless, it depends on ported ESLint rules and is more marketing than practicality.
But I am absolutely exhausted with the breaking changes. Maintaining a config is a nightmare. I don’t understand the point of this new globalIgnores() thing, ignores are still confusing. It doesn’t even work with individual files.

People are saying eslint is dead, yet i get most out of eslint by writing custom rules for it which neither biome nor oxlint support.