@palbase/web 1.8.0 → 1.9.0

package/dist/{analytics-facade-DfJ420F5.d.cts → analytics-facade-DFd5LB3_.d.cts}

@@ -1771,6 +1771,7 @@ declare class PalbeAuth {
     private signingOut;
     private signingIn;
     private signedInState;
+    private hydratingUser;
     private readonly stateListeners;
     private readonly eventListeners;
     private readonly userListeners;
@@ -1788,12 +1789,24 @@ declare class PalbeAuth {
     signOut(): Promise<void>;
     getUser(): Promise<AuthUser>;
     refreshUser(): Promise<AuthUser>;
+    /**
+     * Restore the user after a session was rehydrated from storage (page reload).
+     * Hydration in buildRuntime restores the TOKENS synchronously, but the access
+     * token JWT does not carry emailVerified/createdAt, so the full AuthUser can't
+     * be reconstructed offline — this fetches GET /auth/user once and announces
+     * `signedIn`, so the app no longer has to `await pb.auth.refreshUser()` itself
+     * on boot. Idempotent (runs once), browser-safe (no-op when not signed in or
+     * a user is already cached), and never throws (a boot-time network failure
+     * must not break app startup — isSignedIn stays true, the app can retry).
+     */
+    hydrateUser(): void;
     /**
      * Subscribe to signed-in/signed-out state. Fires immediately with the
-     * current snapshot (iOS parity). NOTE: a restored session (page reload) has
-     * no cached user yet, so the immediate snapshot reports signedOut even when
-     * `isSignedIn` is true — call `refreshUser()` on boot to populate the user
-     * and rely on `isSignedIn` for the session truth.
+     * current snapshot (iOS parity). A restored session (page reload) hydrates
+     * the user asynchronously via `hydrateUser()` (fired once at boot), so the
+     * FIRST snapshot may report signedOut for a tick even when `isSignedIn` is
+     * true; the listener then fires again with `signedIn` once the user lands.
+     * Rely on `isSignedIn` for the session truth if you need it synchronously.
      */
     onAuthStateChange(callback: (state: AuthState) => void): Unsubscribe;
     onAuthEvent(callback: (event: AuthChangeEvent) => void): Unsubscribe;

package/dist/{analytics-facade-CgURkjpP.d.ts → analytics-facade-DsvKx5A5.d.ts}

@@ -1771,6 +1771,7 @@ declare class PalbeAuth {
     private signingOut;
     private signingIn;
     private signedInState;
+    private hydratingUser;
     private readonly stateListeners;
     private readonly eventListeners;
     private readonly userListeners;
@@ -1788,12 +1789,24 @@ declare class PalbeAuth {
     signOut(): Promise<void>;
     getUser(): Promise<AuthUser>;
     refreshUser(): Promise<AuthUser>;
+    /**
+     * Restore the user after a session was rehydrated from storage (page reload).
+     * Hydration in buildRuntime restores the TOKENS synchronously, but the access
+     * token JWT does not carry emailVerified/createdAt, so the full AuthUser can't
+     * be reconstructed offline — this fetches GET /auth/user once and announces
+     * `signedIn`, so the app no longer has to `await pb.auth.refreshUser()` itself
+     * on boot. Idempotent (runs once), browser-safe (no-op when not signed in or
+     * a user is already cached), and never throws (a boot-time network failure
+     * must not break app startup — isSignedIn stays true, the app can retry).
+     */
+    hydrateUser(): void;
     /**
      * Subscribe to signed-in/signed-out state. Fires immediately with the
-     * current snapshot (iOS parity). NOTE: a restored session (page reload) has
-     * no cached user yet, so the immediate snapshot reports signedOut even when
-     * `isSignedIn` is true — call `refreshUser()` on boot to populate the user
-     * and rely on `isSignedIn` for the session truth.
+     * current snapshot (iOS parity). A restored session (page reload) hydrates
+     * the user asynchronously via `hydrateUser()` (fired once at boot), so the
+     * FIRST snapshot may report signedOut for a tick even when `isSignedIn` is
+     * true; the listener then fires again with `signedIn` once the user lands.
+     * Rely on `isSignedIn` for the session truth if you need it synchronously.
      */
     onAuthStateChange(callback: (state: AuthState) => void): Unsubscribe;
     onAuthEvent(callback: (event: AuthChangeEvent) => void): Unsubscribe;

package/dist/{chunk-AWVNDAMG.js → chunk-I3ZMB7XM.js}

@@ -1486,6 +1486,8 @@ var PalbeAuth = class {
   // suppresses AuthClient's TOKEN_REFRESHED during re-signIn
   signedInState = false;
   // dedupes AuthClient's repeated SIGNED_OUT events
+  hydratingUser = false;
+  // guards hydrateUser() to a single boot fetch
   stateListeners = /* @__PURE__ */ new Set();
   eventListeners = /* @__PURE__ */ new Set();
   userListeners = /* @__PURE__ */ new Set();
@@ -1538,13 +1540,37 @@ var PalbeAuth = class {
     if (changed) for (const cb of this.userListeners) this.safeInvoke(() => cb(user));
     return user;
   }
+  /**
+   * Restore the user after a session was rehydrated from storage (page reload).
+   * Hydration in buildRuntime restores the TOKENS synchronously, but the access
+   * token JWT does not carry emailVerified/createdAt, so the full AuthUser can't
+   * be reconstructed offline — this fetches GET /auth/user once and announces
+   * `signedIn`, so the app no longer has to `await pb.auth.refreshUser()` itself
+   * on boot. Idempotent (runs once), browser-safe (no-op when not signed in or
+   * a user is already cached), and never throws (a boot-time network failure
+   * must not break app startup — isSignedIn stays true, the app can retry).
+   */
+  hydrateUser() {
+    if (this.hydratingUser || this.cachedUser || !this.isSignedIn) return;
+    this.hydratingUser = true;
+    void this.refreshUser().then((user) => {
+      if (this.isSignedIn) {
+        this.signedInState = true;
+        this.emitState({ status: "signedIn", user });
+      }
+    }).catch(() => {
+    }).finally(() => {
+      this.hydratingUser = false;
+    });
+  }
   // ── listeners ──────────────────────────────────────────
   /**
    * Subscribe to signed-in/signed-out state. Fires immediately with the
-   * current snapshot (iOS parity). NOTE: a restored session (page reload) has
-   * no cached user yet, so the immediate snapshot reports signedOut even when
-   * `isSignedIn` is true — call `refreshUser()` on boot to populate the user
-   * and rely on `isSignedIn` for the session truth.
+   * current snapshot (iOS parity). A restored session (page reload) hydrates
+   * the user asynchronously via `hydrateUser()` (fired once at boot), so the
+   * FIRST snapshot may report signedOut for a tick even when `isSignedIn` is
+   * true; the listener then fires again with `signedIn` once the user lands.
+   * Rely on `isSignedIn` for the session truth if you need it synchronously.
    */
   onAuthStateChange(callback) {
     this.stateListeners.add(callback);
@@ -8902,7 +8928,7 @@ function defaultSessionStorage(key) {
 }
 
 // src/version.ts
-var VERSION = "1.8.0";
+var VERSION = "1.9.0";
 
 // src/runtime.ts
 function buildRuntime(config) {
@@ -9020,6 +9046,7 @@ function buildRuntime(config) {
   void rt.perf;
   if (typeof document !== "undefined") {
     void new PerfConfigClient().fetchConfig(rt, rt.perf);
+    rt.auth.hydrateUser();
   }
   recordColdStart(rt);
   observeWebVitals((item) => rt.perf.record(item));
@@ -9315,4 +9342,4 @@ export {
   pb,
   createBoundClient
 };
-//# sourceMappingURL=chunk-AWVNDAMG.js.map
+//# sourceMappingURL=chunk-I3ZMB7XM.js.map