ElevenLabs SDK migration
Move from elevenlabs to @elevenlabs/elevenlabs-js: new client, streaming shape, model and voice settings.
1 repository · 3 migrations a month · no card
What compat detects
- @elevenlabs/elevenlabs-js
- elevenlabs
- @elevenlabs/react
- @elevenlabs/client
The package was renamed and the client reshaped around textToSpeech.convert and textToSpeech.stream, with web ReadableStreams replacing Node streams. compat migrates the imports, the calls and the piping code.
What breaks across majors
- 01
elevenlabs renamed to @elevenlabs/elevenlabs-js with a new client shape.
- 02
Model ids and voice settings keys changed.
- 03
Streaming returns a web ReadableStream instead of a Node stream.
- 04
The Conversational AI packages version separately from the core SDK.
Typecheck catches renamed methods. Audio output cannot be verified in CI, so listening checks are manual steps.
What an elevenlabs to @elevenlabs/elevenlabs-js run looks like
Illustrativecompat rewrites imports and client construction, adapts stream handling, keeps model ids to those you name, and opens the pull request with a manual listening check. Illustrative; no public run recorded yet.
01
Detect
compat finds the ElevenLabs packages your code imports and the upstream releases that affect them.
02
Migrate and verify
It edits only the affected code in a disposable sandbox, regenerates the lockfile, and runs your existing tests, type checks, lint and build where available.
03
Pull request
It opens a PR with the diff, verification results, warnings and manual steps. A person merges.
Questions
- Does compat merge the ElevenLabs migration automatically?
- No. compat has no merge capability. It pushes a branch and opens a pull request with the diff, the recorded checks and any manual steps. A person on your team reviews and merges.
- Which checks run?
- Your repository's own: install, typecheck, lint, test and build where the scripts exist. Each is listed in the pull request as passed, failed or not run. A check that did not run is never shown as passed.
- Does compat need my production credentials?
- No. Migrations run in a disposable sandbox with your code and package manager, not your environment. Checks that need live credentials are reported as not run.
- How does compat know a release affects my repository?
- It watches the ElevenLabs packages your code imports, reads new release notes, and judges relevance against the files that actually use the SDK. Irrelevant releases are dismissed with the reason; relevant ones become a proposal or, if you allow it, a run.