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
Hey there! I hope this is the right place to ask for help.
I am trying to deploy an application with Nitro and tRPC with the vercel-edge preset.
I am getting a weird proxy error when I deploy it without making any changes to how tRPC is handled.
TypeError: 'getOwnPropertyDescriptor' on proxy: trap reported non-configurability for property 'setTimeout' which is either non-existent or configurable in the proxy target
at (index.mjs:1:1261145)
at (index.mjs:1:1270611)
at (index.mjs:1:1272087)
at (index.mjs:1:1246628)
at (index.mjs:1:1271597)
at (index.mjs:1:1273439)
at (__nitro:middleware.js:1:17)
I think I need to use the fetchRequestHanlder as described in the tRPC documentation for Fetch / Edge Runtimeshttps://trpc.io/docs/server/adapters/fetch
They provide examples for Next.js, Remix, and SoldStart, but not Nuxt/Nitro.
Nitro uses IncommingMessage and ServerResponse, while the fetchRequestHandler expects a Request and returns a Response.
But again I am getting errors that seem to stem from Nitro using node-fetch under the hood? I am not experienced enough with the edge runtime or nitro to completely understand why it would not work and what needs to happen to make tRPC and Nitro on edge work together.
If anyone has any pointers or if anyone has a repo of a Nuxt/Nitro project that uses tRPC on the edge that would be awesome!
Thanks already for your help!
The text was updated successfully, but these errors were encountered:
goetzrobin
changed the title
tRPC with vercel-edge
Help request: tRPC with vercel-edge
May 31, 2023
Hey there! I hope this is the right place to ask for help.
I am trying to deploy an application with Nitro and tRPC with the vercel-edge preset.
I am getting a weird proxy error when I deploy it without making any changes to how tRPC is handled.
I think I need to use the
fetchRequestHanlder
as described in the tRPC documentation forFetch / Edge Runtimes
https://trpc.io/docs/server/adapters/fetchThey provide examples for Next.js, Remix, and SoldStart, but not Nuxt/Nitro.
Nitro uses
IncommingMessage
andServerResponse
, while thefetchRequestHandler
expects aRequest
and returns aResponse
.My initial, naive approach was to simply map back and forth between the two using these utilities I found for astro: https://github.com/withastro/astro/blob/2dca81bf2174cd5c27cb63cb0ae081ea2a1ac771/packages/integrations/vercel/src/serverless/request-transform.ts#L2
But again I am getting errors that seem to stem from Nitro using
node-fetch
under the hood? I am not experienced enough with the edge runtime or nitro to completely understand why it would not work and what needs to happen to make tRPC and Nitro on edge work together.If anyone has any pointers or if anyone has a repo of a Nuxt/Nitro project that uses tRPC on the edge that would be awesome!
Thanks already for your help!
The text was updated successfully, but these errors were encountered: