\n\n### Link to reproduction\n\nhttps://stackblitz.com/github/trpc/examples-next-minimal-starter\n\n### To reproduce\n\nCan attempt repro if the stack trace provided is not enough\n\n### Additional information\n\n_No response_\n\n### ๐จโ๐งโ๐ฆ Contributing\n\n- [x] ๐โโ๏ธ Yes, I'd be down to file a PR fixing this bug!",[3020,3023,3026],{"name":3021,"color":3022},"๐โโ๏ธ help wanted","008672",{"name":3024,"color":3025},"โฎ needs reproduction","000055",{"name":3027,"color":3028},"๐ bug: unconfirmed","e99695",6533,"trpc","open","bug: Potential memory leak in streaming with v11","2025-02-28T15:50:08Z","https://github.com/trpc/trpc/issues/6533",0.75980633,{"description":3037,"labels":3038,"number":3039,"owner":3030,"repository":3030,"state":3040,"title":3041,"updated_at":3042,"url":3043,"score":3044},"### Provide environment information\r\n\r\n```\r\n System:\r\n OS: macOS 13.4.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 223.42 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.16.0/bin/yarn\r\n npm: 9.8.1 - ~/.nvm/versions/node/v18.16.0/bin/npm\r\n pnpm: 8.6.6 - ~/.nvm/versions/node/v18.16.0/bin/pnpm\r\n Browsers:\r\n Brave Browser: 115.1.56.14\r\n Safari: 16.5.2\r\n npmPackages:\r\n @tanstack/react-query: ^4.18.0 => 4.32.1 \r\n @trpc/client: ^10.36.0 => 10.36.0 \r\n @trpc/next: ^10.36.0 => 10.36.0 \r\n @trpc/react-query: ^10.36.0 => 10.36.0 \r\n @trpc/server: ^10.36.0 => 10.36.0 \r\n next: ^13.4.8 => 13.4.12 \r\n react: 18.2.0 => 18.2.0 \r\n typescript: 5.1.3 => 5.1.3 \r\n```\r\n\r\n### Describe the bug\r\n\r\nWhile using [https://github.com/trpc/trpc/tree/main/examples/next-prisma-todomvc](next-prisma-todomvc) reproduction everything seems to be working fine, however, when I do first request httpUtils gets this error:\r\n\r\n```\r\n \u003C\u003C query #1 user.all {\r\n input: undefined,\r\n result: TRPCClientError: Unexpected token \u003C in JSON at position 0\r\n at TRPCClientError.from (file:///Volumes/DEV/ulobo/node_modules/@trpc/client/dist/TRPCClientError-fef6cf44.mjs:26:16)\r\n at file:///Volumes/DEV/ulobo/node_modules/@trpc/client/dist/httpUtils-ad76b802.mjs:125:36\r\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {\r\n meta: { response: [Response] },\r\n shape: undefined,\r\n data: undefined,\r\n [cause]: SyntaxError: Unexpected token \u003C in JSON at position 0\r\n at JSON.parse (\u003Canonymous>)\r\n at parseJSONFromBytes (node:internal/deps/undici/undici:6571:19)\r\n at successSteps (node:internal/deps/undici/undici:6545:27)\r\n at node:internal/deps/undici/undici:1211:60\r\n at node:internal/process/task_queues:140:7\r\n at AsyncResource.runInAsyncScope (node:async_hooks:203:9)\r\n at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)\r\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n },\r\n elapsedMs: 61\r\n}\r\nTRPCClientError: Unexpected token \u003C in JSON at position 0\r\n at TRPCClientError.from (file:///Volumes/DEV/ulobo/node_modules/@trpc/client/dist/TRPCClientError-fef6cf44.mjs:26:16)\r\n at file:///Volumes/DEV/ulobo/node_modules/@trpc/client/dist/httpUtils-ad76b802.mjs:125:36\r\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {\r\n meta: {\r\n response: Response {\r\n [Symbol(realm)]: null,\r\n [Symbol(state)]: [Object],\r\n [Symbol(headers)]: [HeadersList]\r\n }\r\n },\r\n shape: undefined,\r\n data: undefined,\r\n [cause]: SyntaxError: Unexpected token \u003C in JSON at position 0\r\n at JSON.parse (\u003Canonymous>)\r\n at parseJSONFromBytes (node:internal/deps/undici/undici:6571:19)\r\n at successSteps (node:internal/deps/undici/undici:6545:27)\r\n at node:internal/deps/undici/undici:1211:60\r\n at node:internal/process/task_queues:140:7\r\n at AsyncResource.runInAsyncScope (node:async_hooks:203:9)\r\n at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)\r\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n}\r\n```\r\n\r\n\r\n\r\n### Link to reproduction\r\n\r\nhttps://github.com/porydzaj/trpc-404-httputils\r\n\r\n### To reproduce\r\n\r\nRun first fetch at index with utils/trpc\r\n\r\n### Additional information\r\n\r\n_No response_\r\n\r\n### ๐จโ๐งโ๐ฆ Contributing\r\n\r\n- [ ] ๐โโ๏ธ Yes, I'd be down to file a PR fixing this bug!",[],4671,"closed","bug: Unexpected token \u003C in JSON at position 0","2025-03-20T15:41:49Z","https://github.com/trpc/trpc/issues/4671",0.7228844,{"description":3046,"labels":3047,"number":3052,"owner":3030,"repository":3030,"state":3040,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Provide environment information\n\nSystem:\n OS: macOS 15.0.1\n CPU: (8) arm64 Apple M1 Pro\n Memory: 101.39 MB / 16.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 20.18.1 - ~/.nvm/versions/node/v20.18.1/bin/node\n Yarn: 4.6.0 - ~/.nvm/versions/node/v20.18.1/bin/yarn\n npm: 10.8.2 - ~/.nvm/versions/node/v20.18.1/bin/npm\n bun: 1.2.0 - ~/.bun/bin/bun\n Watchman: 2024.11.04.00 - /opt/homebrew/bin/watchman\n Browsers:\n Chrome: 133.0.6943.127\n Safari: 18.0.1\n npmPackages:\n @trpc/client: ^11.0.0-rc.791 => 11.0.0-rc.791+4eda4d50f\n @trpc/server: ^11.0.0-rc.791 => 11.0.0-rc.791+4eda4d50f\n typescript: ^5.7.3 => 5.7.3\n\n### Describe the bug\n\nWhen using TRPC v11 with the Express adapter, the input received on server (serialized by supersjon on client) can't be correctly deserialized by superjson (eg: Date remains string). By diving into superjson's code, it seems this equality is not met https://github.com/flightcontrolhq/superjson/blob/main/src/is.ts#L16. When creating the exact same input into the transformer (on server side), it works as intended, example : \n```ts\ntransformer: {\n input: {\n serialize: superjson.serialize,\n deserialize: (data: any) => {\n // Artificial input copy\n const foo = {\n \"json\": {\n \"date\": \"2025-02-21T09:33:09.469Z\"\n },\n \"meta\": {\n \"values\": {\n \"date\": [\n \"Date\"\n ]\n }\n }\n }\n\n // Here, date will be transformed into date\n console.log(superjson.deserialize(foo));\n\n // Here, date will not be transformed into date\n return superjson.deserialize(data);\n },\n },\n output: {\n serialize: superjson.serialize,\n deserialize: superjson.deserialize,\n },\n },\n```\n\nIt seems this behaviour appeared in 11.0.0-rc.362, it worked fine on 11.0.0-rc.361 and below.\n\n### Link to reproduction\n\nhttps://github.com/emileNetter/trpc-superjson-repro\n\n### To reproduce\n\n```bash\ncorepack enable\nyarn install\nyarn test\n```\n\nThe test fails because the date can't be converted to Date and zod schema throws an error.\n\n### Additional information\n\n_No response_\n\n### ๐จโ๐งโ๐ฆ Contributing\n\n- [ ] ๐โโ๏ธ Yes, I'd be down to file a PR fixing this bug!",[3048,3049],{"name":3027,"color":3028},{"name":3050,"color":3051},"โณ close if no activity","d4c5f9",6540,"bug: input can't be deserialized by superjson with express adapter","2025-03-18T00:08:02Z","https://github.com/trpc/trpc/issues/6540",0.76187176,{"description":3058,"labels":3059,"number":1598,"owner":3030,"repository":3063,"state":3040,"title":3064,"updated_at":3065,"url":3066,"score":3067},"Hi there,\r\n\r\nThank you for taking the time to put this library together! I just came across an issue when opening the swagger UI - I see errors like so:\r\n\r\n```\r\nCould not resolve reference: #/properties/data/properties/id\r\n```\r\n\r\nFrom looking through the source, it looks like the `zod-to-json-schema` refStrategy (root is the default) is not mapping correctly. Maybe because the entire object is not being passed into the function?",[3060],{"name":3061,"color":3062},"bug","ff3333","trpc-openapi","Schema $refs are not pointing correctly","2022-09-05T09:56:16Z","https://github.com/trpc/trpc-openapi/issues/37",0.766523,{"description":3069,"labels":3070,"number":3074,"owner":3030,"repository":3030,"state":3040,"title":3075,"updated_at":3076,"url":3077,"score":3078},"I have separated libs for client and server, and since @trpc/client doesn't export the observable function and type I also have to install @trpc/server just to use this function and type, which is weird. I think this function should be exported in both packages.",[3071],{"name":3072,"color":3073},"wontfix","ffffff",6013,"feat: @trpc/client should export observable","2024-09-25T12:03:09Z","https://github.com/trpc/trpc/issues/6013",0.7705713,{"description":3080,"labels":3081,"number":3088,"owner":3030,"repository":3030,"state":3040,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### Area of Improvement\r\n\r\nThe Install dependencies section (https://trpc.io/docs/client/react/setup#1-install-dependencies)\r\n\r\nIs listing \r\n`npm install @trpc/server@next @trpc/client@next @trpc/react-query@next @trpc/next@next @tanstack/react-query@latest`\r\n\r\nI believe `@trpc/next@next` should not be included, as this is not anything related to Next?\r\n\r\nI'm not sure, but is `@trpc/server@next` also not required? I tested not installing it and got no errors whatsoever\r\n\r\n### Link to related docs\r\n\r\nhttps://trpc.io/docs/client/react/setup\r\n\r\n### Additional information\r\n\r\n_No response_\r\n\r\n### ๐จโ๐งโ๐ฆ Contributing\r\n\r\n- [ ] ๐โโ๏ธ Yes, I'd be down to file a PR implementing the suggested changes!",[3082,3085],{"name":3083,"color":3084},"๐ documentation / examples","0075ca",{"name":3086,"color":3087},"โ
accepted-PRs-welcome","0052cc",5588,"docs: v11 React Query Integration \"Install dependencies\" section lists unnecessary packages","2025-03-20T15:42:19Z","https://github.com/trpc/trpc/issues/5588",0.7787439,{"description":3094,"labels":3095,"number":3096,"owner":3030,"repository":3030,"state":3040,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Describe the feature you'd like to request\r\n\r\nNB: I'm brand new to trpc, please let me know if this is irrelevant `:)\r\n\r\nIt would be great to be able to stream back parts of result as they become available. Example use cases:\r\n\r\n* Very large queries (of an array of objects), rather than waiting to complete retrieval and send all at once to client.\r\n* Long running tasks, to send strongly typed status messages and task info during the task run.\r\n\r\nTo be clear, I know it's already possible to use `BatchStreamLink` to perform multiple queries and stream the results back of each as they become available. But that's still waits for an individual query to complete. If e.g. a query will contain an array of objects, I want to stream each object back as soon as it's ready, without waiting for the entire array.\r\n\r\n### Describe the solution you'd like to see\r\n\r\nStill thinking this through, but something along the lines of:\r\n\r\n**server.ts**\r\n\r\n```ts\r\n// import { StreamingOutput } from...\r\n\r\nexport const appRouter = t.router({\r\n test: t.procedure.query(() => {\r\n return new StreamingOutput(async (stream) => {\r\n for (let i=0; i \u003C 5; i++) {\r\n stream.emit({ i });\r\n await sleep(1000);\r\n }\r\n stream.close();\r\n }\r\n});\r\n```\r\n\r\n**client.ts**\r\n\r\n```ts\r\nconst client = createTRPCProxyClient\u003CAppRouter>({\r\n links: [ httpStreamingLink(/*.../*) ] // \u003C-- new\r\n});\r\n\r\nconst stream = await client.test.query();\r\n\r\n// as event emitter\r\nstream.on(\"data\", data => doSomethingWith(data));\r\n\r\n// as iterator\r\nfor (const data of stream)\r\n doSomethingWith(data);\r\n```\r\n\r\n### Describe alternate solutions\r\n\r\nI guess there's a more convoluted way of doing this with subscriptions? Or maybe there is another good way but as a new user I don't understand it `:)\r\n\r\n### Additional information\r\n\r\nI apologise for this kind of weird situation where I'm completely new to the project and suggesting new features. I was about to implement something like this in our own internal tooling (which is very similar to tRPC), and thought this could be a good opportunity to rather swap it out for something more maintainable and contribute to the wider community.\r\n\r\nCould I flesh something out as a proof-of-concept? After I have something working, I'd then be grateful for further guidance and love to work together to make it feel more tRPC-like if I miss anything. What do you think?\r\n\r\n*Edit*: Clarify `httpStreamingLink()` in client.\r\n\r\n### ๐จโ๐งโ๐ฆ Contributing\r\n\r\n- [X] ๐โโ๏ธ Yes, I'd be down to file a PR implementing this feature!",[],6050,"feat: streaming array response (to contribute?)","2025-03-20T15:42:35Z","https://github.com/trpc/trpc/issues/6050",0.7788207,{"description":3102,"labels":3103,"number":3105,"owner":3030,"repository":3030,"state":3040,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Provide environment information\n\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700K\n Memory: 11.76 GB / 31.77 GB\n Binaries:\n Node: 22.16.0 - C:\\Program Files\\nodejs\\node.EXE\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\n npm: 10.5.0 - C:\\Program Files\\nodejs\\npm.CMD\n Browsers:\n Edge: Chromium (133.0.3065.92)\n Internet Explorer: 11.0.26100.1882\n npmPackages:\n @tanstack/react-query: ^5.80.7 => 5.80.7\n @trpc/client: ^11.4.3 => 11.4.3\n @trpc/react-query: ^11.4.3 => 11.4.3\n @trpc/server: ^11.4.3 => 11.4.3\n next: ^15.3.3 => 15.3.3\n react: ^19.1.0 => 19.1.0\n typescript: ^5.8.2 => 5.8.3\n\n\n### Describe the bug\n\nI am using Next JS and their App Router.\n\nI have a query that I want to look up a product by matching its name and I want the result to also include the title of the category. When using `mode: \"insensitive\"`, only the fields of Product are provided (but everything works as expected). However, because only the fields of Product are given as a result, typescript does not see the type `product.category.title` or `product.category` for example.\n\nWhat I expect is that although including the mode works with seemingly no issues, the result should include the categories title and not give a typescript error in my IDE and not let me call `product.category`.\n\n### Link to reproduction\n\n*\n\n### To reproduce\n\nCreate a Prisma schema like this:\n```\ngenerator client {\n provider = \"prisma-client-js\"\n}\n\ndatasource db {\n provider = \"postgresql\"\n url = env(\"DATABASE_URL\")\n}\n\nmodel Category {\n id String @id @default(cuid())\n title String @unique\n\n products Product[] @relation(\"CategoryToProduct\")\n}\n\nmodel Product {\n id String @id @default(cuid())\n name String @unique\n\n category Category @relation(\"CategoryToProduct\", fields: [categoryId], references: [id])\n categoryId String\n}\n```\n\nSet up a Query like this:\n```\ngetList: publicProcedure\n .input(z.object({ term: z.string() }))\n .query(async ({ ctx, input }) => {\n return await ctx.db.product.findMany({\n where: {\n name: {\n contains: input.term,\n // mode: \"insensitive\", causes issues not including category\n },\n },\n include: {\n category: {\n select: {\n title: true,\n },\n },\n },\n });\n }),\n```\n\nCall that query (in this case in a server component but most likely an issue in a client component as well): \n```\nconst products = await api.product.getList({term: query});\n```\n\nThen try to call `product.category` within the component.\n\n### Additional information\n\n_No response_\n\n### ๐จโ๐งโ๐ฆ Contributing\n\n- [ ] ๐โโ๏ธ Yes, I'd be down to file a PR fixing this bug!",[3104],{"name":3027,"color":3028},6861,"bug: Prisma - Prisma ORM 'mode: \"insensitive\"' in query","2025-07-17T23:05:21Z","https://github.com/trpc/trpc/issues/6861",0.78135836,{"description":3111,"labels":3112,"number":3113,"owner":3030,"repository":3030,"state":3040,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Provide environment information\r\n\r\n```\r\n System:\r\n OS: macOS 12.5\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 2.67 GB / 32.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n\r\n Binaries:\r\n Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node\r\n npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm\r\n\r\n Browsers:\r\n Chrome: 108.0.5359.124\r\n Safari: 15.6\r\n\r\n npmPackages (Server):\r\n @trpc/server: ^10.4.3 => 10.4.3 \r\n typescript: ^4.9.4 => 4.9.4\r\n\r\n npmPackages (Client):\r\n @tanstack/react-query: ^4.19.1 => 4.19.1 \r\n @trpc/client: ^10.4.3 => 10.4.3 \r\n @trpc/react-query: ^10.4.3 => 10.4.3 \r\n @trpc/server: ^10.4.3 => 10.4.3 \r\n react: ^18.2.0 => 18.2.0 \r\n typescript: ^4.9.4 => 4.9.4\r\n```\r\n\r\n\r\n### Describe the bug\r\n\r\nHey guys,\r\n\r\nFirst of all, thanks for the awesome package, it's been revolutionizing the way we write React apps. \r\n\r\nNot sure if this is a known issue, but return types of queries (and not only) in the client result in `any` when using non-relative (either absolute or TS aliased paths) imports on the server. I supposed it is a bug, since I did not find the docs mentioning relative paths are required.\r\n\r\nActually, if you change the import of the whole `entitiesRouter` to be non-relative (see example and description below), it will return an object of type `any` for `trpc.entities` in the client. So the issue is not only for queries but for anything that is not imported with a relative path in `trpc`.\r\n\r\nThis is kind of frustrating for us, since it requires us to use relative imports pretty much everywhere in the project and it can easily result in a relative imports hell.\r\n\r\nE.g.\r\n`import { A } from '../../../../../../wherever/whatever';`\r\n\r\nIs there a workaround for this and what would it be?\r\n\r\nApologies if this has been asked and answered, I searched through the issues and the docs, but did not find anything.\r\n\r\nRegards,\r\nDelyan\r\n\r\n### Link to reproduction\r\n\r\nhttps://github.com/delyan-peev/trpc-relative-paths-bug\r\n\r\n### To reproduce\r\n\r\n1. Run `npm install` in both the `api-server` and `client` directories.\r\n2. Run `npx prisma generate client` in the `api-server` directory.\r\n3. Observe the returned type of the data property in `client/src/Test.tsx`\r\n4. Change the `import { prisma } from 'prisma';` line in `api-server/routers/entitiesRouter.ts` to `import { prisma } from '../prisma';`\r\n5. Observe the returned type of the data property in `client/src/Test.tsx`\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 fixing this bug!",[],3475,"bug: Procedure return types result in `any` when using non-relative import paths","2022-12-24T16:08:44Z","https://github.com/trpc/trpc/issues/3475",0.78169763,{"description":3119,"labels":3120,"number":3124,"owner":3030,"repository":3030,"state":3040,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Provide environment information\n\n```\n System:\n OS: Linux 6.12 Arch Linux\n CPU: (16) x64 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics\n Memory: 7.71 GB / 30.06 GB\n Container: Yes\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 22.2.0 - ~/.nvm/versions/node/v22.2.0/bin/node **(also tried 23.6.1)**\n Yarn: 1.22.22 - ~/.nvm/versions/node/v22.2.0/bin/yarn\n npm: 10.7.0 - ~/.nvm/versions/node/v22.2.0/bin/npm\n bun: 1.0.3 - ~/.bun/bin/bun\n npmPackages:\n @tanstack/react-query: ^5.64.2 => 5.64.2 \n @trpc/client: 11.0.0-rc.718 => 11.0.0-rc.718+2018e3914 \n @trpc/react-query: 11.0.0-rc.718 => 11.0.0-rc.718+2018e3914 \n @trpc/server: 11.0.0-rc.718 => 11.0.0-rc.718+2018e3914 \n react: ^18.3.1 => 18.3.1 \n typescript: 5.7.2 => 5.7.2\n```\n\n### Describe the bug\n\nWhen using http2, the response body is always empty when the method is POST. I was able to trace the problem and discovered that the reason for this is that the request is being aborted in response to this event:\n\nhttps://github.com/trpc/trpc/blob/776d07336bddd01ac2ad02da0360fb71aa734471/packages/server/src/adapters/node-http/incomingMessageToRequest.ts#L147\n\nIf I don't pass the abort signal in the stream pipe, it is able to write to the stream without any issue and everything works. Here is where I made that change:\n\nhttps://github.com/trpc/trpc/blob/776d07336bddd01ac2ad02da0360fb71aa734471/packages/server/src/adapters/node-http/writeResponse.ts#L50-L52\n\nI'll be honest, it doesn't make sense to me why the response close event fires and yet I can still write it to it just fine. I'm also not sure how to deal with this situation without breaking proper abort handling elsewhere.\n\n### Link to reproduction\n\nhttps://github.com/cseickel/trpc-http2-post-example\n\n### To reproduce\n\nUnfortunately it does not run in stakblitz for me, maybe because it requires an ssl connection. You can clone the linked repo and follow the readme.\n\nhttps://github.com/cseickel/trpc-http2-post-example\n\n### Additional information\n\nI understand that no where does the project explicitly state that HTTP2 is supported, but I'm hoping it is within scope. The reason I want to use HTTP2 is that it is really important for using the SSE subscription feature. The reason for this is that each subscription opens a new connection, and with HTTP/1 the browser will not open more than 6 connections of any type to one server. This limit applies across multiple tabs as well, so it is really hard to stay under that limit. \n\nHTTP/2 removes this limit and makes SSE feasible.\n\nThank you for the awesome project!\n\n\n### ๐จโ๐งโ๐ฆ Contributing\n\n- [x] ๐โโ๏ธ Yes, I'd be down to file a PR fixing this bug!",[3121],{"name":3122,"color":3123},"@trpc/server","9BE78E",6432,"bug: Response not written to POST requests on HTTP2 connection","2025-02-07T12:02:56Z","https://github.com/trpc/trpc/issues/6432",0.7825422,["Reactive",3130],{},["Set"],["ShallowReactive",3133],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYl5sEboOh3uIdUoFLclvw2OiS8stI4txRSkd14iKhT4":-1},"/trpc/trpc/4322"]