}>\r\n \u003CPhotoDetail id={params.id} isModal={false} />\r\n \u003C/Suspense>\r\n \u003C/HydrateClient>\r\n );\r\n}\r\n\r\n```\r\n\r\nClient Component Hook:\r\n\r\n```tsx\r\nexport function useGetPhotoById(id: string) {\r\n return trpc.photos.getPhotoById.useSuspenseQuery(id, {\r\n staleTime: 1000 * 60 * 5,\r\n gcTime: 1000 * 60 * 30,\r\n refetchOnMount: false,\r\n refetchOnWindowFocus: false,\r\n });\r\n}\r\n\r\n```\n\n### Additional information\n\n# Expected Behavior\r\n\r\nThe component should transition smoothly from Suspense fallback directly to the data without showing an empty screen in between.\r\n\r\n# Actual Behavior\r\n\r\nThe loading sequence is:\r\n\r\n1. Suspense fallback (skeleton)\r\n2. Empty screen\r\n3. Actual data\r\n\r\n# Additional Information\r\n\r\n- Using Next.js App Router\r\n- Following RSC patterns from tRPC documentation\r\n- Issue occurs consistently on initial load\r\n- Using latest tRPC RC version (11.0.0-rc.467)\r\n- Using latest React Query version (5.40.0)\r\n\r\nWould appreciate guidance on how to achieve a smooth transition from skeleton to data without the empty screen flash.\n\n### 👨👧👦 Contributing\n\n- [X] 🙋♂️ Yes, I'd be down to file a PR fixing this bug!",[3031],{"name":3032,"color":3033},"🐛 bug: unconfirmed","e99695",6266,"Suspense fallback shows empty screen before data when using prefetch in Server Components","2025-03-20T15:42:44Z","https://github.com/trpc/trpc/issues/6266",0.7144822,{"description":3040,"labels":3041,"number":3042,"owner":3021,"repository":3021,"state":3023,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### Describe the feature you'd like to request\r\n\r\nThere is an [example](https://trpc.io/docs/client/headers) of passing a auth token to `headers` function that will be used on every query and mutation sent to backend.\r\nUnfortunately, the heavy lifting of getting cookies of an already logged-in user to the token client-side is left as an exercise and will probably look like this:\r\n```ts\r\nlet token = typeof window === 'undefined' ? undefined : parseClientCookies(document.cookie).token;\r\nexport function setToken(newToken: string) {\r\n token = newToken;\r\n}\r\nexport const trpc = createTRPCNext\u003CAppRouter>({\r\n config: ({ ctx }) => ({\r\n links: [\r\n httpBatchLink({\r\n url: 'http://localhost:3000/api/trpc',\r\n headers: () => ({\r\n Authorization: typeof window === 'undefined' ? parseServerCookie(ctx.req).token : token\r\n }),\r\n }),\r\n ],\r\n }),\r\n});\r\n```\r\n\r\nIn case of config return being dependant on something like next.js' locale - I don't see a clear solution, though we definitely have locale in the `ctx` object passed to `config` function server-side.\r\n\r\n### Describe the solution you'd like to see\r\n\r\nI suggest adding a `meta` prop (derived from `ctx`) to the `config` parameter that will be universal for both client and server-side.\r\n\r\nServer-side meta is pretty simple:\r\n```diff\r\n+ config meta = getMeta(ctx);\r\n+ const config = getClientConfig({ meta });\r\n- const config = getClientConfig({ ctx });\r\nconst trpcClient = createTRPCClient(config);\r\nconst queryClient = getQueryClient(config);\r\n```\r\n\r\nClient getting meta server-side:\r\n```diff\r\n+ const meta = getMeta(ctx);\r\n+ const getAppTreeProps = (props: Record\u003Cstring, unknown>) => isApp ? { pageProps: props, meta } : props;\r\n- const getAppTreeProps = (props: Record\u003Cstring, unknown>) => isApp ? { pageProps: props } : props;\r\nif (typeof window !== 'undefined' || !opts.ssr) {\r\n return getAppTreeProps(pageProps);\r\n}\r\n```\r\nClient-side using meta:\r\n```diff\r\n+ const WithTRPC = ({ meta, ...props }: AppPropsType\u003CNextRouter, any> & { trpc?: TRPCPrepassProps; meta: TMetaContext }) => {\r\n- const WithTRPC = (props: AppPropsType\u003CNextRouter, any> & { trpc?: TRPCPrepassProps }) => {\r\n const [prepassProps] = useState(() => {\r\n if (props.trpc) {\r\n return props.trpc;\r\n }\r\n\r\n+ const config = getClientConfig({ meta });\r\n- const config = getClientConfig({});\r\n```\r\n\r\n### Describe alternate solutions\r\n\r\nThe alternate solution would be using a specific tool to extract every needed part of a server-side context for each specific case.\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!",[],4649,"feat: pass server-side data to client in WithTRPC HOC","2025-03-20T15:41:48Z","https://github.com/trpc/trpc/issues/4649",0.7287766,{"description":3048,"labels":3049,"number":3053,"owner":3021,"repository":3021,"state":3023,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Describe the feature you'd like to request\n\nI have query procedure `listPosts` which accepts some generic `parameters` and and optional `lastUpdatedAt` timestamp. \r\nThe query key looks something like this:\r\n\r\n```\r\n[[\"posts\",\"list\"],{\"input\":{ \"parameters\": {} },\"type\":\"query\"}]\r\n```\r\n\r\nThis query is expensive, so I cache it also on the server with the given `parameters` as caching key in case multiple clients request the same data. When I receive the same `parameters` on the server, I return the data from the cache.\r\n\r\nNow I need some way for clients to force a refresh on the server returning new data instead of cached data for the same `parameters`. So in this case, I query the `listPosts` with an optional `lastUpdatedAt` timestamp. The query key is now: \r\n\r\n```\r\n[[\"posts\",\"list\"],{\"input\":{ \"parameters\": {}, \"lastUpdatedAt\": 123456789 },\"type\":\"query\"}]\r\n```\r\n\r\nThe servers receives the same `parameters` as before and finds the data in the cache, but the `lastUpdatedAt` timestamp is greater than the cached timestamp. So it runs the expensive operation on the server and returns the new data (and caches it).\r\n\r\nNow I have two query keys on the client which are logically the same. I must update the query data of key 1 and key 2 with new data, because query key 2 is only temporary to trigger a server cache-invalidation. The `lastUpdatedAt` that I sent in query key 2 is a local state that will get lost after page navigation. When I later get back to the `ListPosts` page, it will use query key 1 again with data which was maybe set by query key 2.\r\n\r\nI'm currently using `onSuccess` of `useQuery` to set the query data of all query keys matching the input without `lastUpdatedAt`:\r\n\r\n```ts\r\ntype Input = {\r\n parameters: Record\u003Cstring, any>;\r\n lastUpdatedAt?: number;\r\n};\r\n\r\nconst query = trpc.posts.list.useQuery(input, {\r\n onSuccess(data) {\r\n const { lastUpdatedAt, ...restInput } = input;\r\n // update the query cache for all entries with the same parameters, but ignoring the lastUpdatedAt date\r\n queryClient.setQueriesData(getQueryKey(trpc.posts.list, restInput), data);\r\n },\r\n});\r\n```\r\n\r\nThat means it sets the data for query key 1 (without `lastUpdatedAt`) and 2 (with `lastUpdatedAt`). \r\n\r\n---\r\n\r\nHowever, `onSuccess` was deprecated in React Query v5, so I'm looking for an alternative option. \r\nAllowing to overwrite the generated tRPC query key would make it possible to send different inputs to the server but with the same query key. \n\n### Describe the solution you'd like to see\n\nI would like to overwrite the query key via the tRPC query options:\r\n\r\n```ts\r\nconst query = trpc.posts.list.useQuery(input, {\r\n trpc: {\r\n // static query key overwrite\r\n queryKey: [[\"posts\",\"list\"],{\"input\":{ \"parameters\": {} },\"type\":\"query\"}],\r\n // OR\r\n // dynamic query key overwrite\r\n queryKey: () => {\r\n // remove field that should not be passed to server\r\n const { lastUpdatedAt, ...restInput } = input;\r\n return getQueryKey(trpc.posts.list, restInput)\r\n },\r\n },\r\n});\r\n```\r\n\r\nThat means the following two inputs produce the same query key:\r\n\r\n```ts\r\n// = query key: [[\"posts\",\"list\"],{\"input\":{ \"parameters\": {} },\"type\":\"query\"}]\r\nconst input1 = {\r\n parameters: {},\r\n}\r\n\r\n// = query key: [[\"posts\",\"list\"],{\"input\":{ \"parameters\": {} },\"type\":\"query\"}]\r\nconst input2 = {\r\n parameters: {},\r\n lastUpdatedAt: 123456789\r\n}\r\n```\r\n\r\nBy default, React Query would return the data from the query cache for both inputs. So we would need to use the `refetch()` function to manually trigger a refetch to the server with new input. \r\n\n\n### Describe alternate solutions\n\n1. `useQuery.onSuccess()` was deprecated in v5, but could be implemented again with a `useEffect()` with dependency to `useQuery.data`\r\n\r\n```ts\r\n const { data } = trpc.posts.list.useQuery(input);\r\n\r\n // update all queries every time the data changes\r\n React.useEffect(() => {\r\n const { lastUpdatedAt, ...restInput } = input;\r\n queryClient.setQueriesData(getQueryKey(trpc.posts.list, restInput), data);\r\n }, [data, queryClient, input]);\r\n```\r\n\r\n2. use `useQuery` directly with the proxy client and change the query key\r\n\r\n```ts\r\nconst { lastUpdatedAt, ...restInput } = input;\r\nconst queryKey = getQueryKey(trpc.posts.list, restInput);\r\n\r\nconst query = useQuery({\r\n queryKey,\r\n queryFn: (context) => {\r\n return utils.client.posts.list.query(input)\r\n },\r\n});\r\n```\n\n### Additional information\n\n_No response_\n\n### 👨👧👦 Contributing\n\n- [X] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[3050],{"name":3051,"color":3052},"✅ accepted-PRs-welcome","0052cc",4989,"feat: overwrite query key on trpc.useQuery options","2025-03-20T15:42:01Z","https://github.com/trpc/trpc/issues/4989",0.7344607,{"description":3059,"labels":3060,"number":3061,"owner":3021,"repository":3021,"state":3023,"title":3062,"updated_at":3036,"url":3063,"score":3064},"### Describe the feature you'd like to request\n\nIt would be great to have a trpc link that supports the angular httpClient.\r\nThis would allow angular developers to use the usual interceptors to add headers and similar. Additionally it would also help in SSR use cases as the httpClient can cache requests so that they don't have to be repeated on the client.\n\n### Describe the solution you'd like to see\n\nI think ideally there is a kind of `Client` interface that can be implemented and then dropped into any of the existing links to make sure the requests are sent by the httpCLient.\n\n### Describe alternate solutions\n\nI think alternatively, a new link could be implmented that works with the httpClient.\r\nI tried to implement such a client and it seems to work so far. But since I could not understand the entire model of the current clients, I'm sure it lacks some features. I will paste it here as a reference anyways.\r\n```ts\r\nimport { inject, InjectionToken } from '@angular/core';\r\nimport type { AppRouter } from '@evorto/server/appRouter';\r\nimport { HttpClient } from '@angular/common/http';\r\nimport { CreateTRPCClient, createTRPCClient, TRPCLink } from '@trpc/client';\r\nimport type { AnyRouter } from '@trpc/server';\r\nimport { observable } from '@trpc/server/observable';\r\nimport superjson, { SuperJSONResult } from 'superjson';\r\n\r\nconst TRPC_CLIENT = new InjectionToken\u003CCreateTRPCClient\u003CAppRouter>>(\r\n 'TRPC_CLIENT',\r\n);\r\n\r\nexport interface AngularLinkOptions {\r\n url: string;\r\n}\r\n\r\nconst angularLink = (http: HttpClient) => {\r\n return \u003CTRouter extends AnyRouter>(\r\n opts: AngularLinkOptions,\r\n ): TRPCLink\u003CTRouter> => {\r\n return (runtime) =>\r\n ({ op }) =>\r\n observable((observer) => {\r\n const url = `${opts.url}/${op.path}`;\r\n switch (op.type) {\r\n case 'subscription':\r\n throw new Error('Subscriptions are not supported');\r\n case 'query': {\r\n http\r\n .get\u003C{\r\n result: { data: SuperJSONResult };\r\n }>(url, {\r\n params: {\r\n input: JSON.stringify(superjson.serialize(op.input)),\r\n },\r\n })\r\n .subscribe((res) => {\r\n const parsedResponse = superjson.deserialize(res.result.data);\r\n observer.next({\r\n result: {\r\n type: 'data',\r\n data: parsedResponse,\r\n },\r\n });\r\n observer.complete();\r\n });\r\n break;\r\n }\r\n case 'mutation': {\r\n http\r\n .post\u003C{\r\n result: { data: SuperJSONResult };\r\n }>(url, superjson.serialize(op.input))\r\n .subscribe((res) => {\r\n const parsedResponse = superjson.deserialize(res.result.data);\r\n observer.next({\r\n result: {\r\n type: 'data',\r\n data: parsedResponse,\r\n },\r\n });\r\n observer.complete();\r\n });\r\n break;\r\n }\r\n }\r\n });\r\n };\r\n};\r\n\r\nexport const provideTrpcClient = () => {\r\n return {\r\n provide: TRPC_CLIENT,\r\n useFactory: (http: HttpClient) => {\r\n const link = angularLink(http);\r\n return createTRPCClient\u003CAppRouter>({\r\n links: [link({ url: '/trpc' })],\r\n });\r\n },\r\n deps: [HttpClient],\r\n };\r\n};\r\n\r\nexport function injectTrpcClient() {\r\n return inject(TRPC_CLIENT);\r\n}\r\n```\n\n### Additional information\n\n_No response_\n\n### 👨👧👦 Contributing\n\n- [X] 🙋♂️ Yes, I'd be down to file a PR implementing this feature!",[],6260,"feat: Add a link that uses angulars httpCient","https://github.com/trpc/trpc/issues/6260",0.7376558,{"description":3066,"labels":3067,"number":3068,"owner":3021,"repository":3021,"state":3069,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Provide environment information\r\n\r\n System:\r\n OS: macOS 13.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 119.34 MB / 32.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\n Browsers:\r\n Chrome: 109.0.5414.119\r\n Safari: 16.2\r\n npmPackages:\r\n @trpc/client: ^10.10.0 => 10.10.0 \r\n @trpc/server: ^10.10.0 => 10.10.0 \r\n typescript: ^4.3.5 => 4.7.4 \r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nTRPC client cannot build correctly. Build process exit with: \r\n\r\n```bash\r\nsrc/index.ts(4,14): error TS4023: Exported variable 'getClient' has or is using name 'SerializeObject' from external module \"/Users/aliver/workspace/repo/api-service/node_modules/.pnpm/@trpc+server@10.10.0/node_modules/@trpc/server/dist/shared/internal/serialize\" but cannot be named.\r\n```\r\n\r\n### Link to reproduction\r\n\r\nhttps://stackblitz.com/github/trpc/examples-next-minimal-starter\r\n\r\n### To reproduce\r\n\r\nThis is my code.\r\n```ts\r\nimport { type AppRouter } from './routers';\r\nimport { createTRPCProxyClient, httpLink } from '@trpc/client';\r\n\r\nexport const getClient = (url: string) =>\r\n createTRPCProxyClient\u003CAppRouter>({\r\n links: [httpLink({ url })],\r\n });\r\n\r\n```\r\n\r\n### Additional information\r\n\r\ntrpc version: v10.10.0\r\n\r\n### 👨👧👦 Contributing\r\n\r\n- [ ] 🙋♂️ Yes, I'd be down to file a PR fixing this bug!",[],3740,"closed","bug: TRPC client cannot build correctly","2023-02-22T12:03:14Z","https://github.com/trpc/trpc/issues/3740",0.6418679,{"description":3075,"labels":3076,"number":3083,"owner":3021,"repository":3021,"state":3069,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### Describe the feature you'd like to request\r\n\r\nSince adding tests colocated in `packages/next/app-dir` we now get a bunch of errors when running `p dev` in the `/www`-folder\r\n\r\n\u003Cimg width=\"1358\" alt=\"CleanShot 2023-05-25 at 12 09 18@2x\" src=\"https://github.com/trpc/trpc/assets/459267/9d695cbb-8adb-4e21-9d71-e509d5c1f9b8\">\r\n\r\n\r\n### Describe the solution you'd like to see\r\n\r\nGet rid of them. Ideally without moving the tests.\r\n\r\n### Describe alternate solutions\r\n\r\nno\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!\n\n\u003Csub>[TRP-36](https://linear.app/trpc/issue/TRP-36/chore-get-rid-of-errors-when-running-p-dev-in-www)\u003C/sub>",[3077,3080],{"name":3078,"color":3079},"🕸 www","666FF9",{"name":3081,"color":3082},"😌 QoL","6830B5",4414,"chore: get rid of errors when running `p dev` in `/www`","2023-06-12T12:02:08Z","https://github.com/trpc/trpc/issues/4414",0.65298384,{"description":3089,"labels":3090,"number":3092,"owner":3021,"repository":3021,"state":3069,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Provide environment information\n\n```\r\n System:\r\n OS: macOS 13.5.2\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 271.91 MB / 32.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: 3.6.3 - ~/.nvm/versions/node/v18.16.0/bin/yarn\r\n npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm\r\n Watchman: 2023.09.04.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Chrome: 116.0.5845.187\r\n Safari: 16.6\r\n```\n\n### Describe the bug\n\nWe've seen sporadic error reports in our React Native app of `Cannot read property 'message' of undefined` during construction of a `TRPCClientError`.\r\n\r\nHere's a screenshot from Sentry:\r\n\r\n\u003Cimg width=\"600\" alt=\"image\" src=\"https://github.com/trpc/trpc/assets/712727/c6320116-84b4-4e15-bf9d-67bb4bcd06a2\">\r\n\n\n### Link to reproduction\n\nN/A\n\n### To reproduce\n\nThis occurs sporadically and thus far we've been unable to reproduce this bug reliably in development.\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!",[3091],{"name":3032,"color":3033},4794,"bug: sporadic `Cannot read property 'message' of undefined` when constructing `TRPCClientError`","2025-03-20T15:41:55Z","https://github.com/trpc/trpc/issues/4794",0.69613165,{"description":3098,"labels":3099,"number":3101,"owner":3021,"repository":3021,"state":3069,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Describe the feature you'd like to request\r\n\r\nIt's currently pretty difficult to tell whether a subscription is actually connected and listening for events. To track the status of the connection you would have to handle these events yourself. It would be nice if there was an easier way to track the status of the subscription.\r\n\r\n### Describe the solution you'd like to see\r\n\r\nHave the useSubscription hook return the status of the connection.\r\n\r\n```tsx\r\nconst { status } = api.message.useSubscription();\r\n\r\nif (status !== 'connected') return \u003Cp>You are currently not connected to the server :(\u003C/p>;\r\n\r\nreturn \u003Cp>Connection active :D\u003C/p>;\r\n```\r\n\r\n### Describe alternate solutions\r\n\r\nCurrently to show the user they are not connected to the service I am tracking the online status of the device, but this is only loosely correlated to actual status of the connection. This means that it will always show that the service is available when the device is online even while our service is down.\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!",[3100],{"name":3051,"color":3052},5786,"feat: Make useSubscription return info about the subscription","2025-03-20T15:42:26Z","https://github.com/trpc/trpc/issues/5786",0.69948566,{"description":3107,"labels":3108,"number":3109,"owner":3021,"repository":3021,"state":3069,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Provide environment information\n\n System:\r\n OS: macOS 14.1\r\n CPU: (12) arm64 Apple M3 Pro\r\n Memory: 94.47 MB / 18.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node\r\n Yarn: 1.22.21 - ~/.nvm/versions/node/v20.10.0/bin/yarn\r\n npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm\r\n Watchman: 2023.12.04.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Chrome: 121.0.6167.139\r\n Safari: 17.1\r\n npmPackages:\r\n @tanstack/react-query: ^4.36.1 => 4.36.1 \r\n @trpc/client: ^10.45.0 => 10.45.0 \r\n @trpc/react-query: ^10.45.0 => 10.45.0 \r\n @trpc/server: ^10.45.0 => 10.45.0 \r\n react: 18.2.0 => 18.2.0 \r\n typescript: ^5.1.3 => 5.3.3 \r\n \r\n react-native: 0.73.2\n\n### Describe the bug\n\nHello!\r\n\r\nSee [this line](https://github.com/trpc/trpc/blob/d61ece329f271b69c16a6a262c1979259b7fd366/packages/react-query/src/internals/useHookResult.ts#L16).\r\n\r\nI've followed all these [steps](https://trpc.io/docs/client/react/setup) to setup the tRPC + React Query integration within my React Native application. When attempting to use the `useMutation` hook within a component I'm receiving the following error:\r\n```\r\nCannot assign to read-only property 'path'\r\n```\r\n_Note: using the `useQuery` hook works fine._\r\n\r\nIt's been killing me all day! I'm trying to resolve why the `ref` being passed through is immutable vs mutable but I've not been having much luck.\r\n\r\nI wonder if there's any ideas that spring to mind on your end or whether a change could be required to safely handle this scenario?\r\n\r\nFor now I've commented out the line to continue my local development and all seems to work fine without it.\r\n\r\nReally appreciate the help!\r\n\r\nCheers,\r\nLee\n\n### Link to reproduction\n\nhttps://github.com/LeeBrooks3/trpc-react-native\n\n### To reproduce\n\nI've been unable to reproduce the issue in isolation from my main product monorepo (despite using the same versions of everything), but I've provided a link to the experimental repository anyway - and I continue to investigate.\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!",[],5429,"bug: `Cannot assign to read-only property 'path'` whilst using `useMutation` hook within React Native components","2025-03-20T15:42:14Z","https://github.com/trpc/trpc/issues/5429",0.7005732,["Reactive",3115],{},["Set"],["ShallowReactive",3118],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzbYk6uavzBwfgjdSyNqz8lU6JVmF8LohuDIPgTJ6T3E":-1},"/trpc/trpc/4083"]