chore: update fastify to ^5.0.0

[Fdawgs]

See fastify/fastify#5694

Checklist

• run npm run test and npm run benchmark
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

@Fdawgs can you take a look at why this is failing?

[gurgunday]

Not sure why there is node 10, 16 here?

🚭 Syntax detected in the module is incompatible with the module kind according to the package.json or file extension. This is an error in Node and may cause problems in some bundlers. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/UnexpectedModuleSyntax.md


┌───────────────────┬──────────────────────────────────┐
│                   │ "@fastify/type-provider-typebox" │
├───────────────────┼──────────────────────────────────┤
│ node10            │ 🟢                               │
├───────────────────┼──────────────────────────────────┤
│ node16 (from CJS) │ 🚭 Unexpected module syntax      │
├───────────────────┼──────────────────────────────────┤
│ node16 (from ESM) │ 🟢 (ESM)                         │
├───────────────────┼──────────────────────────────────┤
│ bundler           │ 🟢                               │
└───────────────────┴──────────────────────────────────┘

[Fdawgs]

Issue is that the dist/cjs/index.js file built when running build:cjs has ESM import syntax in it:

"use strict";
import { TypeCompiler } from '@sinclair/typebox/compiler';
import { Value } from '@sinclair/typebox/value';
export * from '@sinclair/typebox';
export const TypeBoxValidatorCompiler = ({ schema, httpPart }) => {
    const typeCheck = TypeCompiler.Compile(schema);
    return (value) => {
        const converted = httpPart === 'body' ? value : Value.Convert(schema, value);
        if (typeCheck.Check(converted)) {
            return { value: converted };
        }
        const errors = [...typeCheck.Errors(converted)];
        return {
            error: errors.map((error) => ({
                message: `${error.message}`,
                instancePath: error.path
            }))
        };
    };
};

Since the last successful release on September 4th, TypeScript 5.6 released, so that may have broken it?
I know TypeScript doesn't follow semver and they put breaking changes in minor releases.

[Fdawgs]

Yep, if i pin typescript to 5.4.5 instead of ^5.4.5 then it's fine.

[climba03003]

I recommend always use ~ for TypeScript since TypeScript use x.y as major version and .z for patch.