`nodeHTTPRequestHandler` stripping out headers, body, and middlewares with Fastify

Hello, we’ve been trying out TRPC on professional projects with Fastify.

We noticed the requestHandler or nodeHTTPRequestHandler is using reply.raw skipping all middleware-defined headers and functionalities including CORS making it unfortunately unusable for production.

according to https://www.fastify.io/docs/latest/Reference/Reply/#raw

.raw
This is the http.ServerResponse from Node core. Whilst you are using the Fastify Reply object, the use of Reply.raw functions is at your own risk as you are skipping all the Fastify logic of handling the HTTP response. e.g.:

as shown on #524

await nodeHTTPRequestHandler({
        req: req.raw,
        res: reply.raw, <----- HERE
        router,
        createContext,
        path: (req.params as any).path,
      });

how can we help ?

thank you

[KATT]

I see. It seems to me like we should provide a lower level primitive for adapters, where the consumer control the flow of the output rather than tRPC doing res directly.

I’ll have a look at this in the next few weeks, for now, shim res as you’re doing. Great that you found a workaround.

[github-actions[bot]]

This issue has been locked because it had no new activity for 14 days. If you are running into a similar issue, please create a new issue. Thank you.