Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the [ESLINT_USE_FLAT_CONFIG] environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
It seems they have moved to a simpler config structure, but for us to use the new versions we have to follow the Configuration Migration Guide.
This issue is to track this task. It should probably include:
bumping the versions of everything eslint and prettier related in the project to latest versions
Update the project to use the new simplified formats
Remove all the references to old config objects which should now be part of the root eslint.configs.js. For example, the package.json scripts should not include the --ext .ts part for all packages in the monorepo in "lint": "eslint . --ext .ts",
Run linting on the project and either fix new lint issues, or apply relevant configuration to disable them.
walter-0
commented
1 week ago
Recently, renovate opened those 2 PRs regarding prettier: #1630 and #1629
Apparently, eslint has a new way of handling configs called flat configs. More info here: https://eslint.org/docs/latest/use/configure/configuration-files-new
In #1629 , part of the changelog includes:
It seems they have moved to a simpler config structure, but for us to use the new versions we have to follow the Configuration Migration Guide.
This issue is to track this task. It should probably include:
eslint.configs.js. For example, the package.json scripts should not include the--ext .tspart for all packages in the monorepo in"lint": "eslint . --ext .ts",