feat: add helper to register TypeBox string formats

[drewnetic]

What’s changed

This PR adds an official helper to register common string formats
(date, date-time, email, uuid, etc.) when using
TypeBoxValidatorCompiler.

Why

Fastify’s default AJV setup enables ajv-formats out of the box,
but TypeBox does not register formats automatically.
This helper avoids copy/paste workarounds and keeps behavior explicit,
without introducing breaking changes.

Notes

• Formats are registered only when the helper is called
• Works for both CJS and ESM builds
• Includes runtime and type tests

Closes #84

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

[drewnetic]

Hi @ilteoood, just a gentle ping on this since it's been a few weeks!

As mentioned below, I had already addressed all your feedback. I just pushed a tiny commit today to fix a small typo in the tests (uri to url) and clean up a stray semicolon.

Everything should be good to go now! Let me know if you need anything else.

[drewnetic]

Hi @ilteoood, just a quick update: I noticed the recent architectural changes for TS 5.9, so I went ahead and rebased this branch to resolve the merge conflicts. Everything is properly migrated to the new .ts setup and all tests are green again. Ready whenever you are! 🚀

[drewnetic]

Hi @ilteoood! Just a gentle ping on this since it's been a while.

I've just rebased the branch to keep it fully up to date with the latest main. During the rebase, I took the opportunity to unify the formats helper directly inside index.ts instead of keeping it in a separate file. This simplifies the CJS/ESM post-build output, removes any extra export overhead, and keeps the package footprint minimal.

All previous feedback has been addressed, and everything is green and ready for another look whenever you have some time. Thank you!

[mcollina]

CI is very red

[drewnetic]

As a side note for the team: while testing locally on Windows (and also via WSL/Ubuntu), npm test consistently failed during the build:test step with the following generic ATTW error:

Cannot read properties of undefined (reading 'filename')

I spent some time debugging this and the package output itself looks correct (npm pack contains all expected files and exports). test:node also passes successfully.

At the moment this seems to be related to attw@0.18.2 behavior in certain local environments rather than the actual package structure/runtime output, although I haven't isolated a minimal reproduction yet.

Just leaving this note here in case someone else hits the same issue locally while reviewing/testing the PR.