rhh4x0R
rhh4x0R•12mo ago

How do pass a 'blob' from frontend to backend?

I'm having trouble doing this without converting an audio Blob to base64 and then decrypting it and creating a file on the server. Base64 is huge and breaks the app, but if I create it client side it's no problem. However I don't want to expose API keys that I need in order to do so (which it does currently). Any ideas on what I could do?
2 Replies
sachin
sachin•12mo ago
https://github.com/trpc/examples-next-formdata
GitHub
GitHub - trpc/examples-next-formdata
Contribute to trpc/examples-next-formdata development by creating an account on GitHub.
rhh4x0R
rhh4x0R•12mo ago
I’ll take a look, thank you.
More Posts
fetch failed - error on npm start on productionI rebuild my next.js app with the npm run build command and I started it with npm start I get thisType return error when using mongoose.node - v16.15.1 npm I'm somewhat new to trpc. Using it with mongoose. Love it so far althought I douseContext won't infer type from tRPC clientI am calling tRPC endpoints from my app and it's working flawlessly. As you can see on first screensForward client headers with createTRPCProxyClient & Server-Side HelpersWith `createTRPCNext` i had the option to tap into the `context.req` object nextjs passed in, but I I have a websocket + REST project. Should I be using splitLink like this to combine WS and HTTP?I have a backend project that uses REST for queries/mutations and Websockets for subscriptions. I jNested procedures are separated by dots, is there a way to change that to `/`s instead ?currently it looks something like this `/api/trpc/post.byId`, is there a way to have it like `/api/tIs there a way to split a trpc api across multiple lambdas ?How do I go about splitting my TRPC api across multiple lambdas, such that each lambda would load thCan I alter the context in a procedure?Is there a proper way to do this? Mutating the `opts.ctx` directly seems wrong