Skip to content

[Drift] SyncStatus uploading/downloading/uploadError/downloadError moved from dataFlowStatus to main interface in JS SDK v2 (powersync-js #999) #515

Description

@benitav

What's changing: In the JS SDK v2 pre-release, uploading, downloading, uploadError, and downloadError move from the dataFlowStatus sub-object on SyncStatus to the main SyncStatus interface, aligning the JavaScript SDK with other PowerSync SDKs. The SyncDataFlowStatus getters are preserved as deprecated members for backward compatibility.

High priority — existing docs are now inaccurate or incomplete

  • Production Readiness Best Practices Guide (https://docs.powersync.com/maintenance-ops/production-readiness-guide) — the "SDK Diagnostics" section states that uploading "can be found on the dataFlowStatus object" and downloading "can be found on the dataFlowStatus object." The Client Logging section contains TypeScript code examples using status.dataFlowStatus?.downloadError and status.dataFlowStatus?.uploadError. In v2, these fields live directly on SyncStatus; accessing them via dataFlowStatus is the deprecated path.

For reviewer consideration — may be worth documenting
None.

Source PR: powersync-ja/powersync-js#999 — merged to the v2 pre-release branch on 2026-06-22.

Filed automatically by Claude Code (claude-sonnet-4-6). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions