Yjs Sync

Connection state machine

disconnected → connecting → connected → disconnected
                   ↓
              disconnected (on error)

Connection steps:

1. Ensure document exists (PUT)
2. Discover snapshot offset
3. Create idempotent producer for writes
4. Start updates stream (SSE or long-poll)
5. Start awareness stream (if configured)

The synced flag is set to true when the server reports upToDate — meaning all existing data has been delivered. It resets to false when local updates are sent, and back to true when those updates echo back.

Core Patterns

Dynamic auth headers

const provider = new YjsProvider({
  doc,
  baseUrl,
  docId,
  headers: {
    Authorization: () => `Bearer ${getAccessToken()}`,
  },
})

Header functions are called per-request. Token refresh works without reconnecting.

Long-poll instead of SSE

const provider = new YjsProvider({
  doc,
  baseUrl,
  docId,
  liveMode: "long-poll", // default is "sse"
})

Switch to long-poll only if your infrastructure buffers or drops SSE streams.

Deferred connection

const provider = new YjsProvider({
  doc,
  baseUrl,
  docId,
  connect: false,
})

// Configure before connecting
provider.on("synced", handleSync)
provider.on("error", handleError)
await provider.connect()

In React, always use connect: false. The provider's async connection flow starts immediately in the constructor, which means events like synced can fire before React's useEffect attaches listeners. With connect: false, you attach listeners first, then call connect() — see the yjs-editors skill for the canonical React pattern.

Error recovery

The provider auto-reconnects on transient errors:

• Network errors → retry with 1s delay
• 5xx server errors → retry with backoff
• Snapshot 404 → rediscover snapshot offset

Errors that do NOT trigger reconnect:

• 401/403 auth errors → emits error event, stays disconnected
• Provider was explicitly disconnected → no reconnect

Common Mistakes

HIGH Using disconnect() instead of destroy() on unmount

Wrong:

return () => provider.disconnect() // Leaks doc/awareness listeners

Correct:

return () => provider.destroy()

disconnect() tears down the network connection but leaves doc.on("update") and awareness.on("update") listeners attached. destroy() calls disconnect() then removes all listeners.

Source: packages/y-durable-streams/src/yjs-provider.ts disconnect() and destroy()

MEDIUM Listening for events that don't exist

The only events are synced, status, and error. There is no snapshot, connected, or disconnected event. Use the status event for connection state changes.

Source: packages/y-durable-streams/src/yjs-provider.ts YjsProviderEvents

HIGH Tension: raw durable streams vs YjsProvider

Use YjsProvider when you need CRDT conflict resolution (collaborative editing, shared state). Use raw stream() from @durable-streams/client when you have append-only data (logs, events, chat messages) where ordering is sufficient and CRDT overhead isn't needed.

See also

• yjs-getting-started — Install and setup
• yjs-editors — TipTap and CodeMirror integration
• yjs-server — Deployment and infrastructure
• reading-streams — Raw stream reading (non-CRDT)
• YJS-PROTOCOL.md — Wire protocol specification