This new version provides an easy path to migrate from ESLint and Prettier. It also introduces machine-readable reports for the formatter and the linter, new linter rules, and many fixes.
This new version provides an easy path to migrate from ESLint and Prettier. It also introduces machine-readable reports for the formatter and the linter, new linter rules, and many fixes.
Cool, I haven’t heard of this, and just recently added eslint and prettier to my new project. I’ll have to give this a shot.
Anyone else have experience with it? I’m worried about scope creep:
Surely it would be easier to leave that to the TypeeScript devs and just focus on linting and formatting, no?
Almost nobody uses the TypeScript compiler for transpilation. I think most people nowadays use either Esbuild or SWC for that. The advantage that Biome has is that we already have the parsing and the serialization infrastructure and can add features like that with relative ease. For users that means fewer dependencies, less configuration, and less room for error.
I guess that’s fair, I’m just concerned about being blocked by something like Biome to use a new TypeScript feature, whereas if it was a separate component, it would be easy to swap for a different dependency with better support.
Maybe that’s not an issue in practice, I don’t know. I’d like an all-in-one solution, I’m just worried about the project running out of steam and not being able to be reused.
It’s a fair concern, but if there’s any consolation, we’re experiencing quite the influx of new contributors lately and the maintainer team is growing every month for the last couple of months. There’s a lot of steam coming our way, so I don’t think we’ll run out just yet :)
Awesome, good to hear. I’ll have to try it out and maybe send some funds your way. :)
❤️