\r\n\t\t\t\u003C/QueryClientProvider>\r\n\t\t\u003C/trpc.Provider>\r\n\t\u003C/React.StrictMode>,\r\n\tdocument.getElementById('root')\r\n)\r\n```\r\n\r\nAnd this is how I am using the hooks inside the\r\n```tsx\r\nconst AppHeader: React.FC = () => {\r\n\tconst { data: school, isLoading } = trpc.useQuery([\r\n\t\t'school.get',\r\n\t\t{ id: schoolId }, //schoolId is a bigint here\r\n\t])\r\n\r\n\treturn \u003C>\u003C/>\r\n}\r\n```\r\nAnd i'm getting this error `Uncaught TypeError: BigInt value can't be serialized in JSON` which shouldn't happen if the transformer was being called. \r\n",[],1979,"react hooks not using data transformer","2022-06-13T23:17:22Z","https://github.com/trpc/trpc/issues/1979",0.7018523,{"description":2914,"labels":2915,"number":2923,"owner":2869,"repository":2869,"state":2888,"title":2924,"updated_at":2925,"url":2926,"score":2927},"I've just merged the #732 & #718 to `main` and released a new V9 draft. \r\n\r\n**Are there any other structural, potentially breaking changes that you would want to get into the next major?**\r\n\r\n- It should be production-ready so feel free to update your deps to `9.0.0-alpha.4`, play around with it, and give me feedback.\r\n- I have tried slowing down on the major version bumps, so I would ideally not do more breaking changes for a while.\r\n- Planning to release `9.0.0` early next week.\r\n- There _might_ come a `10.x` as well later in a month or so in order to add support for SvelteKit - might require some major changes as their API handlers are a bit different.\r\n\r\n\r\n> If you're happy you can just give a 👍 on this issue.\r\n\r\n## Summary of changes so far\r\n\r\n- Middlewares will now have to call a `next()` function that you **have to** call.\r\n- Reduce `TRPCError`s - `METHOD_NOT_FOUND` removed & `PATH_NOT_FOUND` renamed to `NOT_FOUND` (#733)\r\n- Align input and output serialization (#746)\r\n- Remove deprecated `httpErrors`-helper \r\n- Remove support for `?input` to be an array - now assuming a `Record\u003Cnumber, unknown>`-style dict (changed with backward compat in #669)\r\n- Remove support for `POST` calls being `{ input: x }` (originally from #671)\r\n- 🛬 Incoming as well\r\n - #811 \r\n - #816 \r\n - #820 ",[2916,2919,2922],{"name":2917,"color":2918},"🙋♂️ help wanted","008672",{"name":2920,"color":2921},"💬 discussion","4B318A",{"name":2879,"color":2880},810,"tRPC v9 feedback before marking it as `9.0.0`","2022-10-04T18:08:32Z","https://github.com/trpc/trpc/issues/810",0.70712537,{"description":2929,"labels":2930,"number":2932,"owner":2869,"repository":2869,"state":2888,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Area of Improvement\n\ni get some problem while develop at this statck. can some one add a example of this tech stack\n\n### Link to related docs\n\n_No response_\n\n### Additional information\n\n_No response_\n\n### 👨👧👦 Contributing\n\n- [ ] 🙋♂️ Yes, I'd be down to file a PR implementing the suggested changes!",[2931],{"name":2866,"color":2867},6647,"docs: add examples of: trpc + react-router7(remix) + cloudflare","2025-04-03T08:10:34Z","https://github.com/trpc/trpc/issues/6647",0.70763713,{"description":2938,"labels":2939,"number":2940,"owner":2869,"repository":2869,"state":2888,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### Describe the feature you'd like to request\n\nstricter typings for [transformTRPCResponseItem](https://github.com/trpc/trpc/blob/c1b3844de8f366fb8c0409e7a12c5a104e8616ab/packages/server/src/internals/transformTRPCResponse.ts#L4)\n\n### Describe the solution you'd like to see\n\nInference for the `router` parameter in the `transformTRPCResponseItem` function.\r\nSomehow typing `_def` to have a `transformers` field of type [`CombinedDataTransformer`](https://github.com/trpc/trpc/blob/c1b3844de8f366fb8c0409e7a12c5a104e8616ab/packages/server/src/transformer.ts#L14).\n\n### Desribe alternate solutions\n\nI worked around this in my app ([a template that wires up vite-electron-trpc-prisma ](https://github.com/NickyMeuleman/electron-trpc-prisma)) where I had to copypaste the `transformTRPCResponseItem` function by using the appRouter for my app directly, but that wouldn't be possible in the library code.\n\n### Additional information\n\n\r\n\r\nI don't have much TypeScript knowledge, and am wondering what the recommended way to achieve this might be.\n\n### 👨👧👦 Contributing\n\n- [X] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[],2804,"feat: typings for transformTRPCResponseItem","2022-12-11T18:01:47Z","https://github.com/trpc/trpc/issues/2804",0.70765597,{"description":2946,"labels":2947,"number":2951,"owner":2869,"repository":2869,"state":2888,"title":2952,"updated_at":2953,"url":2954,"score":2955},"Shall we spruce up the docs both here & on the official docs site? \r\n\r\nThere was a lovely dumpster fire of a thread over on /r/programming where people just did not understand what this was for.\r\n\r\nI won't link the thread directly here unless prompted (not sure of the rules etc) but here's a few areas of confusion / places people had questions about;\r\n- Did not know it was for fullstack TS. \r\n- Did not know if it was just for REST API's\r\n- Why this over GraphQL / using something like protobuf\r\n- Confusion over the name\r\n\r\n",[2948,2949,2950],{"name":2866,"color":2867},{"name":2917,"color":2918},{"name":2898,"color":2899},2223,"clarifying trpc comparisons and what it does","2022-11-03T12:02:36Z","https://github.com/trpc/trpc/issues/2223",0.70841247,{"description":2957,"labels":2958,"number":2959,"owner":2869,"repository":2869,"state":2888,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Describe the feature you'd like to request\r\n\r\nCurrently, when uploading `formData` in tRPC with `zod-form-data`, transformers such as `SuperJSON` attempt to parse the data even when it is `NonJsonSerializable`. This disrupts the handling of `formData`, causing validation errors.\r\n```\r\n[\r\n {\r\n \"code\": \"invalid_type\",\r\n \"expected\": \"string\",\r\n \"received\": \"undefined\",\r\n \"path\": [\"name\"],\r\n \"message\": \"Required\"\r\n },\r\n {\r\n \"code\": \"custom\",\r\n \"message\": \"Input not instance of File\",\r\n \"fatal\": true,\r\n \"path\": [\"image\"]\r\n }\r\n]\r\n```\r\n\r\nI would like to suggest a feature that allows toggling the transformer on a per-router basis or automatically disabling it when the input data meets the `isNonJsonSerializable` condition. This could help prevent unnecessary parsing and improve handling of non-JSON serializable data types.\r\n\r\n\r\n### Describe the solution you'd like to see\r\n\r\n```\r\nexport const roomRouter = router({\r\n sendMessage: publicProcedure\r\n .disableTransformer() // add option to disable transformer somewhere\r\n .input(uploadFileSchema)\r\n .mutation(async (opts) => {\r\n return {\r\n image: await writeFileToDisk(opts.input.image),\r\n };\r\n }),\r\n});\r\n```\r\n\r\n### Describe alternate solutions\r\n\r\nThe only solution I’ve found so far is to not use the transformer altogether.\r\n\r\nI tried to bypass transformer when an object is `isNonJsonSerializable` like this:\r\n```\r\nconst transformer = {\r\n serialize: (object) => {\r\n if (isNonJsonSerializable(object)) {\r\n return object;\r\n }\r\n return SuperJSON.serialize(object);\r\n },\r\n deserialize: (object) => {\r\n if (isNonJsonSerializable(object)) {\r\n return object;\r\n }\r\n return SuperJSON.deserialize(object);\r\n },\r\n};\r\n\r\n```\r\nHowever, this approach didn’t work because simply calling the transformer itself seems to set the body to undefined and stop the file stream. (I'm not entirely sure, but that’s what it seems like)\r\n\r\n### Additional information\r\n\r\nYou can reproduce the issue in [this fork](https://github.com/ZetabS/examples-next-formdata-transformer)\r\n\r\nSteps to Reproduce\r\n1. Clone the repository and install dependencies.\r\n2. Run the development server.\r\n3. Attempt to upload formData with an image.\r\n\r\n### 👨👧👦 Contributing\r\n\r\n- [x] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[],6225,"feat: Toggle Transformer per Router","2025-03-20T15:42:42Z","https://github.com/trpc/trpc/issues/6225",0.70847315,{"description":2965,"labels":2966,"number":2967,"owner":2869,"repository":2968,"state":2888,"title":2969,"updated_at":2970,"url":2971,"score":2972},"Hi thanks for the awesome package!\r\n\r\nI am still a beginner using tRPC and am using this package to incrementally add a trpc layer into my projects.\r\nI was wondering if there is a possibility of using compression algos such as gzip to the body response.\r\nI understand that [data transformers](https://trpc.io/docs/data-transformers) are not supported, but is this out of scope due to how trpc would compress as discussed [here](https://github.com/trpc/trpc/issues/1925)? \r\n\r\nIt seems like something that isn't really applicable to normal tRPC\r\n\r\n",[],173,"trpc-openapi","Understanding compression compared to normal openapi ","2022-11-15T12:41:46Z","https://github.com/trpc/trpc-openapi/issues/173",0.70857227,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f33J98Rskj_INyHvYKRUuWVuV4fpvcBd3Pmm7bN31e4E":-1},"/trpc/trpc/3276"]