bun runtime & liveQuery

server log

verbose: Support key pairs
parse-server-example running on port 1337.
info: Parse LiveQuery Server started running
verbose: Request: {"type":"Buffer","data":[123,34,111,112,34,58,34,99,111,110,110,101,99,116,34,44,34,97,112,112,108,105,99,97,116,105,111,110,73,100,34,58,34,109,121,65,112,112,73,34,109,121,65,112,112,73,100,34,44,34,109,97,115,116,101,114,75,101,121,34,58,34,109,121,77,97,115,116,101,114,75,101,121,34,44,34,105,110,115,116,97,108,1000,34,58,34,98,97,51,55,98,97,116,105,111,110,73,100,34,58,34,98,97,51,55,97,55,51,97,45,51,53,97,53,45,52,99,97,57,45,97,56,98,56,45,57,48,49,98,50,97,99,51,53,101,102,98,34,125]}
verbose: Push Response : "{"op":"error","error":"Missing required property: op","code":1,"reconnect":true,"requestId":null}"
error: Connect message error Missing required property: op

buffer content

{"op":"connect","applicationId":"myAppI"myAppId","masterKey":"myMasterKey","instal�":"ba37bationId":"ba37a73a-35a5-4ca9-a8b8-901b2ac35efb"}

suggested

how add a custom method for parsing socket messages?

Start with the server log and the reported buffer content, then locate the LiveQuery socket message handling and how Bun delivers socket data. Determine whether the malformed buffer is produced during parsing or before it reaches the parser. Done means the cause and required parsing behavior are established, with a reproducible verification for the reported connection message.