[insin]

I think it depends on how overboard you go on the ESLint + plugins config than anything.

For a project I worked on, the main benefit was not having to manage (the 1,000 line haircut to package-lock.json was appreciated) and wire together the ESLint dependencies, and the ones to make it work with TypeScript, and the ones for plugins during our (ok, only my) regular…

    npx --yes npm-check-updates --interactive --format group

…sessions. Migrating was just switch the dependencies and keep adding rules you do/don't care about to biome.json until you can live with it, but we didn't go that mad with the ESLint config prior to that.

I've had more issues with the VS Code extension than anything, not picking up config files when you think it should, needing restarted sometimes due to things like the import sorting on save (which to be fair is marked as experimental) completely breaking and producing malformed code near the imports you changed, and just being a bit… complainy if you had projects with and without a biome.json in your workspace.