non-json-content-types

Handle file uploads and binary data in tRPC mutations by using octetInputParser on the server to convert binary inputs to ReadableStream and routing requests with splitLink on the client. This avoids manual encoding and JSON parsing limitations.

Yes, you can send FormData directly to a tRPC server mutation. The backend uses octetInputParser to read FormData fields and binary streams, while the client uses splitLink and isNonJsonSerializable to ensure proper data routing.

The best way to route non-JSON requests in tRPC is using splitLink combined with isNonJsonSerializable on the client. This safely directs FormData and binary payloads to the server, bypassing standard JSON serialization.

No, tRPC does not support binary streams and FormData for queries. The octetInputParser and splitLink configuration enforces that FormData and binary inputs are only supported for POST mutations, not query operations.

You need splitLink for tRPC file uploads to route non-JSON payloads safely. It works with isNonJsonSerializable to direct binary streams and FormData to the server via octetInputParser, preventing standard JSON serialization errors.

octetInputParser processes binary inputs on the tRPC server by converting incoming binary data into a ReadableStream. This allows mutations to directly handle file uploads and FormData without relying on JSON parsing.