Skip to content

feat: migrate to Deepgram JS SDK v5#1

Open
naomi-deepgram wants to merge 2 commits intomainfrom
update/sdk-v5
Open

feat: migrate to Deepgram JS SDK v5#1
naomi-deepgram wants to merge 2 commits intomainfrom
update/sdk-v5

Conversation

@naomi-deepgram
Copy link
Copy Markdown

Summary

  • Bumps @deepgram/sdk from v3 to 5.0.0-beta.4 in deno.json
  • Updates all SDK call sites to the new v5 API
  • Regenerates deno.lock to reflect the new dependency tree
  • deno-text-intelligence also gains upfront URL validation (format check + pre-fetch) to correctly return 400 for invalid/unreachable URLs rather than propagating a 500 from the Deepgram API — this brings it in line with the other starters

Testing

This PR was tested thoroughly before being opened:

Automated conformance tests — run locally against a live server using the starter-contracts test suite:

  • All conformance tests pass ✅

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.4 pre-release. It will be updated to pin the stable 5.0.0 release as soon as it ships.

@naomi-deepgram naomi-deepgram changed the title feat: migrate to Deepgram JS SDK v5 beta feat: migrate to Deepgram JS SDK v5 Mar 5, 2026
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/analyzeUrl
- URL analysis now uses body.url instead of a separate method
- Remove deno.lock (will be regenerated on first run)
@naomi-deepgram naomi-deepgram marked this pull request as ready for review March 5, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants