oRPC v2 migration feedback: what hurt, and what should change before stable?

[dinwwwh]

oRPC v2 is at 2.0.0-beta.49. Before it goes stable, we'd like to hear from anyone who has migrated from v1, or tried to.

Migrating from v1

• What broke, and how long did it take to fix?
• What was missing or unclear in the migration guide?
• Is anything keeping you on v1?

Before stable

Stable is the last chance to rename or reshape APIs without another major version.

• Which APIs feel awkward, verbose, or inconsistent?
• What do you need that is still experimental or missing?
• Did a recent beta break something it shouldn't have?

Please include the packages you use (@orpc/openapi, @orpc/tanstack-query, ...) and a code snippet where it helps. One comment per topic makes replies and upvotes easier.

Try the beta:

npm install @orpc/server@beta @orpc/client@beta

Docs: https://orpc.dev · v1 docs: https://v1.orpc.dev · Releases: https://github.com/middleapi/orpc/releases

[timvandam]

Not a huge fan of the removal of status from errors. Makes sense in the context of RPC but when REST is your primary concern. Is there a way to keep the v1 behavior/close to it through interceptors?

No issue with anything else

[dinwwwh]

Not just for RPC. It also helps maintain consistency between the status and error code, avoiding misleading behavior and unnecessary complexity.

That said, you can still access the status on the client if you need it: https://orpc.dev/docs/openapi/link#error-responses