Request Handler blowing up when using Node v24? #1289
Replies: 2 comments
-
|
Hi @JinxedStar! I'm Dosu and I’m helping the orpc team. This is a known issue with orpc and recent Node.js versions like v24. The error happens when there are multiple copies of a class with private fields (for example, from plugins like BodyLimitPlugin) loaded in your runtime—often due to module duplication in monorepos, Next.js, or when using Turbopack. JavaScript can't access private fields across different copies, so you get the "Cannot read private member #state" error. To fix it: make sure you only have one copy of Recent orpc releases are tested with Node v24, but this error can still occur if deduplication isn't ensured. Let me know if you want step-by-step deduplication help or troubleshooting tips. Reference: module duplication and private field error To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Can you help me create minimal repro without only Node.js + oRPC (without 3rd)? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Our team has been using orpc and love it! We just started a new project and wanted to update all of our deps to the latest stuff so we don't fall behind :)
However, when we upgraded to node v24 we got weird errors and tracked it down to the RPCHandler not liking the new Request object or something?
Is this a known problem or did we somehow mess up something in our configs/etc?
Thanks everyone!
Beta Was this translation helpful? Give feedback.
All reactions