I also skipped dealing with ESLint in favor of Biome.
The experience is quite nice. Rules have few options, which reduces the time needed to adjust parameters.
With Biome 2.0 (currently in Beta), Biome introduces plugin support. Unlike ESLint, where plugins may repeatedly parse code to an Abstract Syntax Tree (AST) due to the flexibility in tool choice, Biome Plugins will be written in GritQL. This approach leaves the AST unmodified and allows efficient querying, potentially avoiding the inefficiencies caused by repeated parsing. While GritQL may not cover all ESLint plugin functionalities initially, it is designed to handle most use cases effectively.
I use Zed+Biome.js, and I'm happy with Biome.
One caveat: Biome requires a GitHub Action when using in a workflow. At least in my set up, npm seems to be not able to run Biome after installing dependencies. Fortunately, the Biome team hosts an official Github Action.
nerdalytics 3 days ago. link 1 point ▲ ▼