@pylonsync/react 0.3.303 → 0.3.304

package/dist/db.d.ts

@@ -19,6 +19,25 @@ import { type UploadedFile } from "./index";
 export declare function init(config?: Partial<SyncEngineConfig> & {
     baseUrl?: string;
 }): void;
+/**
+ * Switch the active session token and re-sync the local replica to the new
+ * identity. Call this on EVERY auth transition — login, signup, AND logout
+ * (pass `null`).
+ *
+ * It writes the token where both the request helpers and the sync engine read
+ * it, then wipes the local replica — dropping the previous identity's pending
+ * offline writes so they can't replay as the new user — and re-snapshots under
+ * the new identity.
+ *
+ * Why this exists: changing the stored token alone is NOT enough. The engine is
+ * already running with the previous identity's replica + cursor; without an
+ * explicit reset it keeps serving that (or, after a re-init, an empty replica on
+ * a stale cursor) — so the rows the new user should see never load and freshly
+ * written rows appear to "vanish" on the next render/refresh. This is the
+ * supported, can't-get-it-wrong way to flip identity; hand-rolling token writes
+ * without it is the #1 cause of "my data disappears after login" in Pylon apps.
+ */
+export declare function setSessionToken(token: string | null): Promise<void>;
 /** Module-internal accessor for the global sync engine. Exported so
  *  hooks living outside this file (e.g. `useRoom`) can share the same
  *  engine instance and benefit from the same lazy-start / lazy-init

package/dist/index.d.ts

@@ -20,7 +20,7 @@ export { useSession } from "./useSession";
 export type { UseSessionReturn, ResolvedSession } from "./useSession";
 export { useSyncStatus } from "./useSyncStatus";
 export type { SyncConnectionStatus } from "./useSyncStatus";
-export { db, init, getSync } from "./db";
+export { db, init, getSync, setSessionToken } from "./db";
 export { createTypedDb } from "./typed";
 export type { TypedDb, AgentDBSchema } from "./typed";
 export { SyncEngine, createSyncEngine, getServerData, LocalStore, MutationQueue, } from "@pylonsync/sync";

package/package.json

@@ -3,7 +3,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.3.303",
+  "version": "0.3.304",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./dist/index.d.ts",
@@ -13,8 +13,8 @@
     "prepack": "bun run build"
   },
   "dependencies": {
-    "@pylonsync/sdk": "0.3.303",
-    "@pylonsync/sync": "0.3.303"
+    "@pylonsync/sdk": "0.3.304",
+    "@pylonsync/sync": "0.3.304"
   },
   "peerDependencies": {
     "react": ">=19.0.0"

package/src/db.ts

@@ -24,6 +24,8 @@ import {
 import {
   callFn,
   configureClient,
+  getReactStorage,
+  storageKey,
   streamFn,
   uploadFile,
   uploadFileMultipart,
@@ -75,6 +77,40 @@ export function init(config?: Partial<SyncEngineConfig> & { baseUrl?: string })
   });
 }
 
+/**
+ * Switch the active session token and re-sync the local replica to the new
+ * identity. Call this on EVERY auth transition — login, signup, AND logout
+ * (pass `null`).
+ *
+ * It writes the token where both the request helpers and the sync engine read
+ * it, then wipes the local replica — dropping the previous identity's pending
+ * offline writes so they can't replay as the new user — and re-snapshots under
+ * the new identity.
+ *
+ * Why this exists: changing the stored token alone is NOT enough. The engine is
+ * already running with the previous identity's replica + cursor; without an
+ * explicit reset it keeps serving that (or, after a re-init, an empty replica on
+ * a stale cursor) — so the rows the new user should see never load and freshly
+ * written rows appear to "vanish" on the next render/refresh. This is the
+ * supported, can't-get-it-wrong way to flip identity; hand-rolling token writes
+ * without it is the #1 cause of "my data disappears after login" in Pylon apps.
+ */
+export async function setSessionToken(token: string | null): Promise<void> {
+  const key = storageKey("token");
+  const store = getReactStorage();
+  if (token) store.set(key, token);
+  else store.remove(key);
+  // resetReplica wipes rows + cursor (wipeMutations drops the outgoing
+  // identity's queued writes) so the previous identity's data is gone
+  // immediately. The re-snapshot pull runs in the BACKGROUND (not awaited) — for
+  // a large replica it can take a moment, and blocking login on a full snapshot
+  // is bad UX; live `useQuery`/`useSearch` hooks show loading and populate as the
+  // snapshot lands. Awaiting resetReplica (fast) is enough for callers.
+  const engine = getSync();
+  await engine.resetReplica({ wipeMutations: true });
+  void engine.pull();
+}
+
 /** Module-internal accessor for the global sync engine. Exported so
  *  hooks living outside this file (e.g. `useRoom`) can share the same
  *  engine instance and benefit from the same lazy-start / lazy-init

package/src/index.ts

@@ -118,7 +118,7 @@ export { useSyncStatus } from "./useSyncStatus";
 export type { SyncConnectionStatus } from "./useSyncStatus";
 
 // One-liner API
-export { db, init, getSync } from "./db";
+export { db, init, getSync, setSessionToken } from "./db";
 
 // Typed client (consumes generated AppSchema)
 export { createTypedDb } from "./typed";