Draft
Conversation
Update @deepgram/sdk from 4.11.3 to 5.0.0-beta.4 and migrate
API calls to the new v5 interface:
- DeepgramClient constructor instead of createClient factory
- read.v1.text.analyze instead of read.analyzeText
- Options and body merged into single request object
- Errors thrown as exceptions (no { result, error } pattern)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@deepgram/sdkfrom v3 to5.0.0-beta.4deepgram.listen.prerecorded.transcribeFile/transcribeUrl→deepgram.listen.v1.audio.transcriptions.create, etc.)pnpm-lock.yamlto reflect the new dependency treeTesting
This PR was tested thoroughly before being opened:
Automated conformance tests — run locally against a live server using the
starter-contractstest suite:Manual end-to-end testing — the full stack (backend + frontend) was spun up locally and tested interactively via the UI, confirming meaningful responses from the Deepgram API.
Note
This PR targets the
5.0.0-beta.4pre-release. It will be updated to pin the stable5.0.0release as soon as it ships.