Nextjs App Router example repo doesn't match NextJS App Router Docs
#❓-help
The official documentation on how to use NextJSs App Router at:
https://trpc.io/docs/client/react/server-components...
Problem using EventEmitters [Weird behavior]
I'm trying to implement a simple notification in a webapp, I can't make it work with EventEmmiters
```js
streamNotifications: publicProcedure.subscription(async function* (opts) {
try {...
Solution:
I use redis for my project https://github.com/bebore/ei-noah-bot but that's quite complex, I recommend just following the redis package docs. It's not much different from the event emitter other than that you need to (de)serialize the input and output.
Migrating to use Superjson
I currently have a tRPC router that is being used by a web app & React native client. My current version does not use superjson. I want to start using superjson as my transformer. Is there an easy way for me to make this migration?
When I tried just starting to use Superjson, our React native client started running into errors because the old mobile client was not using superjson but the server was. I wish I could access context in my transformer so I could choose to only do the transformation for new clients. Any other ideas on how I can make the switch-over while maintaining backwards compatibility for older clients?...
Type safe errors?
Hi, it's there a way to make something like this in Trpc?
```typescript
import { useQuery } from "@tanstack/react-query"
import type { InferResponseType } from "hono"
...
Can I get a mutations input type form my client?
Hey friends, I'm working on an angular app with tanstack query and trpc. I'm trying to solve duplication and have one central repository (service) of query options. For this I am using a service and it would be amazing to get the input type for my procedures.
```ts
@Injectable({
providedIn: 'root',
})...
Output typings in Monorepo always resolve to any
I’m using a monorepo and pnpm workspaces to import my router into the FE code. However the typings for the output will always resolve to any - the inputs will resolve find but the outputs (schema or no schema) won’t. I’ve followed the advice on the documentation, any suggestions?
Image upload using TRPC
Do wehave any examples to upload image to s3 and store the url in out db using trpc.
I'm using nextjs with trpc server....
I'd love to brainstorm about #5580
I just personally ran into the issue described here(https://github.com/trpc/trpc/issues/5580) and would love to see if anyone has any ideas on potential solutions.
My app size is large enough now that I need to have
disableSourceOfProjectReferenceRedirect enabled, which leads to the behavior described in that post, with Go-To-Definition completely broken, even with type source maps available....can't create context when using nextjs app dir
Im trying to use the latest version of nextjs and make use of the app directory. when trying to make a create context function like they show in the docs here: https://trpc.io/docs/server/context , it gives the following error when i try to create the handler on the frontend
...
Types of parameters 'opts' and 'opts' are incompatible.
Property 'res' is missing in type 'FetchCreateContextFnOptions' but required in type 'CreateNextContextOptions'
Types of parameters 'opts' and 'opts' are incompatible.
Property 'res' is missing in type 'FetchCreateContextFnOptions' but required in type 'CreateNextContextOptions'
subscriptions on edge
Trpc SSE subscriptions does not work on edge for me. Is there some specific config i need to implement?
I have followed the guide for subscriptions on trpc docs (https://trpc.io/docs/server/subscriptions)...
Turn off batching for some queries?
Hiya, I have a use case where I want to set headers on specific queries (specifically
cache-control private for authenticated data that's requested frequently by the client across page reloads) but because of batching, I'd need to make sure requests to these queries are never batched so the headers only refer to the one query at a time.
Are there any tricks for this? Or any better approaches for my use case?...Error: This is a client-only function.
It was working last week in
11.0.0-rc.660 but in 11.0.0-rc.682 it's not. I didn't change any code. I just rolled back and confirmed.
```ts
const createCaller = createCallerFactory(this.router);
const caller = createCaller(socket.ctx);...Disable explicit content-type checks
Hey, using TRPC v11 in a production ready system. We've got an external service that sends a notification to an exposed REST endpoint on our server, using trpc-to-openapi. However, the content-type is application/x-www-form-urlencoded and v11 does check for that. Is there any way to disable this check or allow specific content-types?
Optimizing Global State Updates for Mutations Across Multiple Query Keys in tRPC with React Query
I'm using tRPC with React Query in my app, and I need some advice. I have a mutation (e.g., toggleLike) that updates a specific field (hasLiked) for posts. The mutation works fine, and I'm using optimistic updates to reflect the changes immediately in the UI.
Here's the challenge:
I need this hasLiked field to update consistently across multiple query keys, such as getLatest and getTrending, whenever the mutation is triggered. Right now, I have to manually update each query like this:
...
SuperJSON not tranforming dates in edge runtime
I switched trpc routes to edge runtime in nextjs, and now the superjson transformer doesn't work. Has anyone else ecountered this probelm and found a solution?
trpc doesn't work after migrating to next 15
When i upgraded to Next 15 (pages router), all trpc routes fails with status 500 on production. The result message is
{"error":{"json":{"message":"req.socket.once is not a function","code":-32603,"data":{"code":"INTERNAL_SERVER_ERROR","httpStatus":500}}}}. I don't really understand if it's TRPC issue, Next issue or even Netlify issue (i host my website there, but they declare to support Next 15). Does anybody have an idea where the problem could be? I don't call req.socket.once anywhere in m...Express/NextJS Server Side Setup
After following the T3Repo TRPC setup, I attempted to modify it for an Express API. Everything works great except... on server side requests it runs the backend as it imports createCaller from the backend.
I have been lost trying to configure the NextJS Config and TSConfig to see if I can get out of this but I am out of ideas.
```ts...
subscription tracked returns a 3-tuple to frontend instead of object
I am using
tracked as per recommendation in https://trpc.io/docs/server/subscriptions#tracked like this:
```ts
for await (const [eventData] of iterable) {
yield tracked(eventData.jobId, eventData);
}...Example on Website has no Output Types
In this example from the website https://trpc.io/docs/quickstart#try-it-out-for-yourself
there is no output type nference. If i download it its the same. For example in the index.ts in the client users has no type.
...
const users = await trpc.user.list.query();
const users = await trpc.user.list.query();
TRPC Error does not say router path
Hello,
I have a tRPC client that sometimes fails to call my procedures/queries. I have many of them and find difficult to track back the router path that failed. Am I missing something? In the stacktrace I only get this:
TRPCClientError: Unexpected token 'A', "An error o"... is not valid JSON...