You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a trpc client to make server (express5) to server (fastify4 + trpc) calls. There are cases where it works but they are mostly getting stuck and calls never finish despite fastify4's successful answer.
To fix that I found out that I can customise the fetch and use node-fetch IF i ignore the typescript error.
Is that a bug? Shouldn't it be working out of the box? Shouldn't node-fetch be compatible?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I use a trpc client to make server (express5) to server (fastify4 + trpc) calls. There are cases where it works but they are mostly getting stuck and calls never finish despite fastify4's successful answer.
To fix that I found out that I can customise the fetch and use node-fetch IF i ignore the typescript error.
Is that a bug? Shouldn't it be working out of the box? Shouldn't node-fetch be compatible?
I will try to make a reproducible project
System:
OS: Linux 6.8 Linux Mint 22.1 (Xia)
Binaries:
Node: 22.16.0 - ~/.nvm/versions/node/v22.16.0/bin/node
npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm
pnpm: 10.13.1 - ~/.nvm/versions/node/v22.16.0/bin/pnpm
Watchman: 4.9.0 - /usr/bin/watchman
Browsers:
Chromium: 138.0.7204.168
npmPackages:
@trpc/client: ^11.4.3 => 11.4.3
@trpc/server: ^11.4.2 => 11.4.3
typescript: ^5.8.3 => 5.8.3
Beta Was this translation helpful? Give feedback.
All reactions