@vafanassieff is attempting to deploy a commit to the ts-rest Team on Vercel.

A member of the Team first needs to authorize it.

⚠️ No Changeset found

Latest commit: e3e610c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

Hey, any news about this one ?

Hey @oliverbutler, sorry to bother you and thanks for this awesome repository.

Can you give us some information about the maintenance / evolution of ts-rest, it seems like it's been almost 5 months since there has been a new version, are there any reasons for this ? Will it continue like this ? Should we consider making an official fork for the repository ?

In advance thanks for your answers, I wish you all the best for your projects 🪻

@this-is-tobi npm install @ts-rest/fastify --legacy-peer-deps works for this was able to get it running.

A ping again to @oliverbutler, I was able to use v5 without issue with my routers

Hi @vafanassieff! Thanks for the PR.

Unfortunately due to the breaking changes in fastify v5, it seems like this would be a major version change to @ts-rest.

This may be a case of needing a @ts-rest/fastify v5 much like we've done for react-query v5.

What do you think?

Hey, if we follow the semver spec it's indeed a major release, only for the @ts-rest/fastify package.

@vafanassieff yup, however, we follow a single version policy so we have the exact same versions cross all of our packages (due to type sharing)

We'll likely have to copy/paste the fastify lib and make a v5.

I'm unsure whether our standard will be to have the v5 impl within the fastify lib e.g. @ts-rest/fastify/v5 or whether we just add a new @ts-rest/fastify-v5 package.

@Gabrola went with the /v5 subpath pattern with react-query so would be good to get that one agreed before moving forwards with this pr.

any updates on this?, i was very happy fastify was supported by ts-rest and then i found this issue 😂 😂 😂 😂

Thanks to all the maintainers ❤️

I would love for this change to land, given it's more or less trivial.

Waiting for this change

I don’t think this needs to be a breaking change. The library remains compatible with fastify v4, so users don’t have to upgrade to fastify v5. The only required adjustment is to relax the version constraint in the package.json to allow fastify >= 4.0.0.

Or am I overlooking something?

I just started implementing a backend with ts-rest v3.52.1 and fastify v5.4.0. Things are working fine so far (I am just in initial stages). But following pnpm warning lead me to this feature request thread.

 WARN  Issues with peer dependencies found
xyz-backend
└─┬ @ts-rest/fastify 3.52.1
  └── ✕ unmet peer fastify@^4.0.0: found 5.4.0

I have read the comments and now I am confused whether to continue with it or not.

Same, i didn't have any issues so far.

Maybe just relax the version constraint?

Any chance this can get over the line 🙏

Looks like just the version constraint needs relaxing?

@oliverbutler Is there anything that can be done to help push this over the finish line? I'm happy to help create separate fastify5 package if that is how is preferable to proceed.

Btw, I've created an alternative PR that avoids breaking changes and just bumps the range: #850

It should work at a runtime, but produce non-ideal types for Replies. Full solution would require merging this PR in some form.