goetzrobin•15mo ago

Nitro and tRPC in vercel-edge

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)

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 Runtimes https://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. 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!

Fetch / Edge Runtimes Adapter | tRPC

You can create a tRPC server within any edge runtime that follow the WinterCG, specifically the Minimum Common Web Platform API specification.

GitHub

astro/request-transform.ts at 2dca81bf2174cd5c27cb63cb0ae081ea2a1ac...

The all-in-one web framework designed for speed. ⭐️ Star to support our work! - astro/request-transform.ts at 2dca81bf2174cd5c27cb63cb0ae081ea2a1ac771 · withastro/astro

2 Replies

Nick•15mo ago

It might be our proxy doesn't currently support this setup, but I'm really not familiar with this tech If your conclusion is the proxy needs some changes then I'd open an issue (PRs also very welcome)

goetzrobin•14mo ago

Thanks for getting back to me! I haven’t found a solution/fix for this as it’s really hard to debug since this only happens in said edge environment. In theory the vercel edge should be supported as mentioned in the docs: https://trpc.io/docs/server/adapters/fetch. But I haven’t had any luck so far. If I find anything I’ll open an issue/PR Can you point me to the files in the source code where that proxy you mentioned is created? Thanks already!