Skip to main content
If you’re upgrading from v0.1.3, this guide walks you through the two breaking changes you need to address. The migration is straightforward (mostly find-and-replace).

What Changed


Breaking Change 1: Direct Property Access

In v0.1.3, all properties were wrapped in a .meta object. In v0.2.0, properties are accessed directly on the instance.

Video

Audio

Image

Collection

Shot (Search Results)

Migration shortcut: Search your codebase for .meta. and replace with . for each class type.

Breaking Change 2: Async/Await Pattern

In v0.1.3, long-running operations returned Job objects that required callback registration. In v0.2.0, these are standard async functions. The SDK handles polling internally, errors propagate through try/catch, and there’s no risk of silent failures from unregistered error handlers.

Getting Transcripts

Indexing Spoken Words

Uploading Media

Error Handling


Removed Exports

The following exports no longer exist in v0.2.0:
If your code imports any of these, remove the imports and refactor to use await directly on the method calls.

Migration Checklist

Property Access

1

Search for .meta. patterns

Use your IDE or grep to find all occurrences of .meta. in your codebase.
2

Replace with direct access

  • video.meta.*video.* - audio.meta.*audio.* - image.meta.*image.* - collection.meta.*collection.* - shot.meta.*shot.*

Job Pattern

1

Remove Job imports

Delete imports for Job, TranscriptJob, UploadJob, IndexJob, waitForJob
2

Remove callback registrations

Delete .on('success', ...) and .on('error', ...) blocks
3

Remove .start() calls

Delete any job.start() or await job.start() calls
4

Add await to method calls

Change const job = video.getTranscript() to const transcript = await video.getTranscript()
5

Update error handling

Wrap calls in try/catch instead of using .on('error', ...)

Complete Example


Need Help?

GitHub Issues

Report bugs or ask questions

Discord Community

Get help from the community