Kranga
Kranga•8mo ago

Subscription types are not inferred while queries and mutations are working fine

I am NOT working with a monorepo but while query and mutation types are being inferred out of the box on the client side, subscriptions are always inferred as any no matter how simple their types are.
No description
2 Replies
Kranga
Kranga•8mo ago
This is the subscription implementation, it is just attaching a listener to an event emitter via a simple wrapper class. I even tried being pedantic with the types but it does not work
No description
Kranga
Kranga•8mo ago
The subscription input type is z.void() but I don't think it makes any difference
More Posts
How are thrown (unhandled) exceptions safe to pass?Hi, I started looking into error handling more and understand that all errors get wrapped in a TRPCECanary useUtils and createTRPCQueryUtils type not callableTrying to access utils object in my application after using `useUtils` or `createTRPCQueryUtils` andtRPC run express under the hood?tRPC run `expressjs` under the hood?Modify mutation error messages?We occasionally get timeouts from cloudfront which gives the user an error about how the cloudfront server-side helpers doesnt work with `Hydrate` and `QueryClient`environtment: node v20.9.0, npm Hi i tried to implement server-side helpers but somehow it just doesUnable to mock unstable_batchStreamLink network responseHi there! I have a couple API endpoints that call third party dependencies and would like to mock a