We could add `Biome` using `pre-commit` to save CI and developer time

https://biomejs.dev

Biome is a [fast formatter](https://github.com/biomejs/biome/tree/main/benchmark#formatting) for JavaScript, TypeScript, JSX, TSX, JSON, HTML, CSS and GraphQL that scores [97% compatibility with Prettier](https://console.algora.io/challenges/prettier), saving CI and developer time.

So we have JS, JSON and CSS at least:

https://biomejs.dev/internals/language-support/

Mostly written in Rust:

https://github.com/biomejs/biome

https://biomejs.dev/recipes/git-hooks/#pre-commit

It seems much more configurable than Prettier and you can configure settings for individual file types

Why do we use use tools like Biome and prettier:

"By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. [It is generally accepted that having a common style guide is valuable for a project and team](https://www.smashingmagazine.com/2012/10/why-coding-style-matters/) but getting there is a very painful and unrewarding process. People get very emotional around particular ways of writing code and nobody likes spending time writing and receiving nits."

https://prettier.io/docs/why-prettier

Start with the Biome language-support and pre-commit recipe links in the issue, then inspect the repository's existing formatting and CI configuration. Done would require an agreed Biome integration scope and corresponding project configuration, but the issue names no files or tests.

Written by the indexing model from the issue text.