issue with websockets? #8462
Unanswered
jjmaldonis
asked this question in
Q&A
Replies: 3 comments
-
@jjmaldonis did you ever find a solution for this (or your customer?) |
Beta Was this translation helpful? Give feedback.
0 replies
-
@jjmaldonis I also tried using Deepgram SDK with bun a few days ago and ran into quite a few issues with websocket connections |
Beta Was this translation helpful? Give feedback.
0 replies
-
@cleanbaja @nicolas-angelo Unfortunately we never found a solution. The customer swapped back to Node and stopped using Bun. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey Bun, I work at Deepgram and while on a recent customer call we discovered that Bun does not support our JS SDK.
You can find reproducible example code here: https://github.com/deepgram/deepgram-js-sdk/blob/main/examples/node-live/index.js
The example accepts microphone audio input and sends the audio to Deepgram. Deepgram then transcribes the audio (speech to text) and returns a JSON message to the user containing the words in the audio.
When running this code via Node you'll see transcripts printed to the terminal.
When running the same code via Bun the websocket connection closes immediately. It looks like Bun has special syntax for websockets. I know the customer tried for days trying to get it to work following your documentation, and he was very tech-savvy.
We wanted to flag this for your team in case it's relevant.
Beta Was this translation helpful? Give feedback.
All reactions