Biome vs ESLint — Which one do you prefer and why?

[Abdullah-dev0]

Hey everyone 👋

I’ve been exploring different tools for linting and formatting in JavaScript/TypeScript projects. Recently, I came across Biome — it claims to be a faster and more modern alternative to ESLint (and even replaces Prettier in some cases).

I’d love to hear your thoughts:

• Have you tried Biome yet?
• How does it compare to ESLint in real-world projects?
• Any major pros/cons or migration issues?

I’m considering using it in a new project, so any insights or experiences would be super helpful 🙏

[tmilost]

I haven't tried Biome, ESLint works great + Prettier, there were problems, but nothing complicated that I couldn't solve very quickly.

Feature	Biome	ESLint
Speed	🚀 Very Fast	🐢 Slower
Ecosystem	🌱 Growing	🌳 Mature
TypeScript Support	👍 Good (some limits)	👍 Excellent
Customizability	👌 Simpler, less	💪 Very flexible
Plugin Support	🚸 Limited	🏆 Extensive
Formatting	🧹 Built-in	Separate (Prettier)

[tmilost]

Go ahead and experiment with Biome in your new project. If you decide to revert, the migration path to ESLint isn't complicated. Just be prepared that a format change will likely be a significant commit that touches many files and could clutter your Git blame/history

[jdmarshall]

As a frequent git archaeologist, commits that only touch formatting and introduce no behavioral changes make things a lot easier for subsequent readers. You can configure git to ignore specific commit IDs as well if it really bothers you. But that fails if you mix fixes and formatting, or squash PRs. So file a PR just do to the whitespace changes and nobody will curse your existence.