\r\n}\r\n\r\n```\r\n\r\n## Advantages\r\n- the action and server component query function could be exported and reused in other components\r\n- The nicest part would that the function maybe integrated to the trpc router at some point: \r\n```ts\r\n// example with the previous defined functions\r\nexport const ordersRouter = t.router({\r\ncreateOrder: t.procedure.implement(createOrder),\r\ngetUserOrders: t.procedure.implement(getUserOrders) \r\n })\r\n\r\n// note: implement is here a magic method that knows to add it correcly to the router. \r\n// the specifics of this implement function are left-aside, but I think it should be possible\r\n```\r\n\r\n\r\n\r\n### Describe alternate solutions\r\n\r\nother possible libaries: \r\n- https://github.com/pingdotgg/zact\r\n- https://github.com/TheEdoRan/next-safe-action\r\n\r\nHowever, I think TRPC could be the best solution (if it integrates with the app router)\r\n\r\n### Additional information\r\n\r\nI would really like to see suggestions or other enhancements and become aware of what the plans are with TRPC in the context of next 13.4!\r\n\r\n### 👨👧👦 Contributing\r\n\r\n- [ ] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[3001],{"name":3002,"color":3003},"duplicate","cfd3d7",4431,"feat: React Server Components & Server Actions ","2023-05-26T20:18:23Z","https://github.com/trpc/trpc/issues/4431",0.6924253,{"description":3010,"labels":3011,"number":3012,"owner":2922,"repository":2922,"state":2984,"title":3013,"updated_at":3014,"url":3015,"score":3016},"### Describe the feature you'd like to request\r\n\r\nFollowing #3482 & coming over from https://github.com/typescript-eslint/typescript-eslint/issues/6760: typescript-eslint is soon going to release a new v6 major version with reworked configurations. You can read up on it here: [typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta](https://typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta)\r\n\r\nSpecifically, the [configurations are reworked](https://typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta#reworked-configuration-names) so that the recommended equivalents to what trpc uses now are:\r\n\r\n* `'plugin:@typescript-eslint/recommended-type-checked'`\r\n* `'plugin:@typescript-eslint/stylistic-type-checked'`\r\n\r\n### Describe the solution you'd like to see\r\n\r\nI can send a PR updating to them!\r\n\r\n### Describe alternate solutions\r\n\r\nI suppose trpc could stay on typescript-eslint@v5, or use its own bespoke lint configs... neither option seems very appealing to me. 😄 \r\n\r\n### Additional information\r\n\r\n_No response_\r\n\r\n### 👨👧👦 Contributing\r\n\r\n- [X] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[],4540,"feat: Use typescript-eslint@v6 & its reworked configs","2025-03-20T15:41:45Z","https://github.com/trpc/trpc/issues/4540",0.70956075,{"description":3018,"labels":3019,"number":3020,"owner":2922,"repository":2922,"state":2984,"title":3021,"updated_at":3022,"url":3023,"score":3024},"### Describe the feature you'd like to request\n\nThis feature request is based on a discussion between @KATT and @marcusradell: \r\n https://discord.com/channels/867764511159091230/1077176270678401035/1088065480339763210\r\n\r\nTo sum it up, we don't use singletons in our codebase, but wrap all code in functions.\r\nSince tRPC recommends `export type AppRouter = typeof appRouter`, we had to create our own custom TrpcRouter type.\r\n\r\nOur solution stopped working when upgrading from tRPC v10.4.3 to v10.17.0 as `RouterDef` was no longer exported publicly. Getting more official support from tRPC would mean that we don't have to use types we don't fully understand, and enable more devs to use types that don't require singleton code.\r\n\r\nA small note: it's not that bad that tRPC uses the singleton pattern. But the patterns leaks into the rest of our layers, which is the real issue.\n\n### Describe the solution you'd like to see\n\nHere is a minimal example repo that you can run (`npm i` and `npm run dev`):\r\nhttps://github.com/WP-Tech-AB/trpc_app_router_type\r\n\r\nThe TrpcRouter is what we want better support for out of the box, and maybe a Trpc type. See this line for context:\r\nhttps://github.com/WP-Tech-AB/trpc_app_router_type/blob/main/src/trpc.ts#L21\r\n\r\nWe used a bunch of `any` types as we aren't sure what to put there instead.\n\n### Describe alternate solutions\n\nJust make `RouterDef` a public export again.\n\n### Additional information\n\nWe don't know enough to contribute a general solution, but we have everything of value in our example code, and you are free to pick what you want and use in tRPC.\n\n### 👨👧👦 Contributing\n\n- [ ] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[],4075,"feat: Static AppRouter type","2023-04-07T18:01:55Z","https://github.com/trpc/trpc/issues/4075",0.7226135,["Reactive",3026],{},["Set"],["ShallowReactive",3029],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTWsXWc4PC0ZpNPGvQVYn-J6daLe64pUJfhBhnT6eduw":-1},"/trpc/trpc/5493"]