Deepgram's JavaScript SDK hits v5 with breaking changes and a migration guide
- Source
- x.com
- Date
Deepgram’s JS SDK v5.0.0 is now officially stable and live on npm. This major release includes breaking changes, and teams upgrading from v4 should review the migration guide before updating. The guide is complete and ready to support a smooth transition. What’s new in v5: ✅ Regenerated codegen architecture with stronger type safety ✅ Native support for both browser and Node.js environments ✅ Stable Voice Agent v1 interfaces, including Nova-3 support ✅ Nova-3 available across STT ✅ Flux support ✅ DEEPGRAM_ACCESS_TOKEN authentication (aligned across SDKs) ✅ Additional controls including filler words, speak fallback, mip_opt_out, ttl_seconds, and more Install with: `npm install @deepgram/sdk@latest` Full details are available on npm and GitHub, along with the v4 → v5 migration guide.
Context
Upgrading Deepgram's JavaScript library from version 4 to version 5 requires application changes. The migration guide replaces createClient with DeepgramClient, reorganizes calls under versioned API names and changes error handling to exceptions handled with try/catch. integrations also need revised connection and message handling. These changes affect how an application starts a transcription request and receives its results, so changing the installed package alone does not complete the migration.
- streaming — Sending a model's response token by token as it is generated, so the reader sees text immediately instead of waiting for the whole answer.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
- token — The chunk of text a model reads and writes in — roughly three-quarters of a word — and the unit AI usage is billed in.
Checking sign-in…
Loading comments…