You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moreover, the framework using Zod validation and allowing only string, which fails to parse ArrayBuffer or any binary data. Here's an example from the server side where data is being parsed as a string:
As I'm not an expert, I might be missing something, but from what I can see, it doesn't seem to support binary data. If there is a way to achieve this functionality, I would appreciate any guidance, or it may be worth considering adding support for binary data in future releases.
The text was updated successfully, but these errors were encountered:
Hey! As a workaround for transmitting the blob directly, you could upload to a third-party storage (e.g., S3, R2) from the client, and then transmit the URL after upload. Could you elaborate on the use case a bit?
It seems that binary data (such as audio or video blobs) cannot be transmitted from the client to the server using WebSockets.
Upon debugging, I found that the client is stringifying the data before sending it through the websocket.
This leads to binary data being lost, and the data becomes an empty object {}.
File affected:
packages/jstack-shared/src/event-emitter.ts.
Moreover, the framework using Zod validation and allowing only string, which fails to parse ArrayBuffer or any binary data. Here's an example from the server side where data is being parsed as a string:
As I'm not an expert, I might be missing something, but from what I can see, it doesn't seem to support binary data. If there is a way to achieve this functionality, I would appreciate any guidance, or it may be worth considering adding support for binary data in future releases.
The text was updated successfully, but these errors were encountered: