Echo JS 0.11.0

At this point, I pretty much just use Biome for linting and formatting.  ESLint just got too slow on a few large projects.

Biome seems promising but a little short on config and plugins.

Could you elaborate more on how you use it? 

In particular if you have a casse for custom pattern. 

Eg: let say on a specific class type you want always the constructor empty and the params optional. Could you do that in Biome?

I don't change too much with my Biome config... I can say that when I first started, the config options were really hard to figure out without examples, but I think the documentation has expanded since then.  I don't know about your specific case.

I would probably defer to typescript annotations if you want to start setting arguments as optional for a constructor or given methods.  I will usually assign a manual default if I want typed behavior.  But that will involve adding the TS compiler in addition to Biome, which only partially checks TS.

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.