feat: initial implementation

[climba03003]

Checklist

• run npm run test && npm run benchmark --if-present
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

Resolved

[Eomm]

IDK, neostandard isn't fast to ship the new eslint version, but another linting config is "boring"

[Tony133]

I see that this PR is open: fastify/fastify#6923 maybe something is moving on neostandard 👀

[climba03003]

IDK, neostandard isn't fast to ship the new eslint version, but another linting config is "boring"

Upgrading or depending on ESLInt is a disaster in every major update. It requires over a year for all plugin to be prepared.

I would not force the old repository to use biome, but it is not the first one using it. website already using biome for linting. It should not be a blocker for using it in new repository.

The configuration of biome is simple, I use recommended configuration for linting and the formatting rules is actually a copy of .editorconfig.