Post

I don't know how a migration helper from a static json file the new flat config can fail so horribly. Does anybody have a successful migration story for a non-trivial .eslintrc.json to flat config?

Remco Haszing

@remcohaszing.nl

9 Oct 2025

I migrated my reusable config manually. But I also made some other non-trivial changes, such as swapping out some plugins and updating existing ones. Having a reusable config made updating consuming repos a breeze.

Sebastian Silbermann

@sebbie.dev

9 Oct 2025

Do you have a PR to share?

Remco Haszing

@remcohaszing.nl

9 Oct 2025

Not a PR, but this was the release. I did some other breaking changes and internal restructuring as well, so the diffs are messy. github.com/remcohaszing...

github.comRelease v11.0.0 · remcohaszing/eslintThis is a complete overhaul with rules in the same spirit. Some notable changes: This project was renamed to @remcohaszing/eslint. This project now requires Node.js 22. This project now requires E...

Sebastian Silbermann

@sebbie.dev

sounds like a rewrite not migration

9/10/25, 9:39 pm0 reposts1 like

Remco Haszing

@remcohaszing.nl

9 Oct 2025

The rulesets are largely the same. I use some stylistic plugins, so I switched some rules to @stylistic/eslint-plugin or eslint-plugin-perfectionist. eslint-plugin-import-x is a drop in replacement for eslint-plugin-import. And I no longer felt the need for eslint-plugin-react for this project.