oRPC Monorepo Playground

[dinwwwh]

Describe the change

A playground that follow best practices mentioned here: https://orpc.unnoq.com/docs/best-practices/monorepo-setup

URLs

No response

Additional information

• Would you be willing to help?

[unbiased-dev]

👍 We really need this especially around context. Like for example if core-service is a package, and server is an app, and we need to inject runtime context (like db connection or orm or auth context) and these are inferred in server it feels like a chicken and the egg problem since the router needs to be context aware inside the package but that live in server which imports the core-service package.

[dinwwwh]

@unbiased-dev In my opinion, everything a package depends on place in corresponding packages too. In your case, db can be placed in core-contract along with the database schema. For auth, it's simpler - you can just define the core-service context to depend on something like user?: { id: string }. This can be a callback, and when you import core-service it in the server, you simply provide the necessary context.

[hunterwilhelm]

I made an oRPC Monorepo example with Vue 3 and Bun. Feel free to try it out!

https://github.com/hunterwilhelm/orpc-community-playgrounds

Issue: #1129
PR: #1130

[maelp]

Would be nice to have a oRPC + Hono + Pino + otel monorepo as a starter example!

[dinwwwh]

Here yours: https://github.com/unnoq/orpc-multiservice-monorepo-playground (still working on)