@tumbaland/frontend-core 1.6.1 → 1.8.0

package/dist/authService.js

@@ -1,5 +1,30 @@
 import { getCorrelationId, getSessionId, logger } from './monitoring';
+import { clearSessionScopedStorage } from './sessionStorage';
 const AUTH_CACHE_TTL = 5 * 60 * 1000;
+/**
+ * Tell the shell its session just ended.
+ *
+ * Each app runs in the shell's iframe with its own copy of this module, so a
+ * logout inside the frame clears only the frame's cache and reloads only the
+ * frame. The shell keeps serving its own five-minute-old `authenticated:
+ * true` from memory, which is why signing out and clicking home still showed
+ * the signed-in page instead of the landing page.
+ *
+ * The message carries nothing, so `'*'` gives nothing away; the shell is the
+ * side that authenticates it, by origin and by frame (see `useShellBridge`).
+ */
+function notifyShellOfLogout() {
+    if (typeof window === 'undefined' || window.parent === window.self)
+        return;
+    try {
+        // Contract lives in @tumbaland/components `routing/messages` — a lower
+        // layer cannot import it, so the literal is repeated here.
+        window.parent.postMessage({ source: 'tumbaland-app', type: 'app:logout' }, '*');
+    }
+    catch (error) {
+        logger.warn('Failed to notify shell of logout', { error });
+    }
+}
 function authHeaders() {
     return {
         'Content-Type': 'application/json',
@@ -81,6 +106,8 @@ export function createAuthService(config) {
                 if (data.success) {
                     authCache = null;
                     authCacheTime = 0;
+                    clearSessionScopedStorage();
+                    notifyShellOfLogout();
                     window.location.reload();
                 }
                 return data.success;

package/dist/index.d.ts

@@ -5,5 +5,6 @@ export type { AuthServiceConfig, AuthService, AppAuthConfig } from './authServic
 export { createGroupService } from './groupService';
 export type { GroupServiceConfig, GroupService } from './groupService';
 export type { User, AuthResponse, Group, ApiResponse } from './types';
+export { TENANT_STORAGE_KEY, clearSessionScopedStorage } from './sessionStorage';
 export { initMonitoring, captureException, captureMessage, setUser, setTag, startTransaction, recordMetric, initWebVitals, flushLogs, initConsoleInterception, generateCorrelationId, getCorrelationId, getSessionId, logger } from './monitoring';
 export type { MonitoringConfig } from './monitoring';

package/dist/index.js

@@ -2,5 +2,6 @@
 export { createApiClient, ApiError } from './apiClient';
 export { createAuthService, createAppAuthService } from './authService';
 export { createGroupService } from './groupService';
+export { TENANT_STORAGE_KEY, clearSessionScopedStorage } from './sessionStorage';
 // Monitoring: headless logging, error capture, correlation IDs, and web-vitals
 export { initMonitoring, captureException, captureMessage, setUser, setTag, startTransaction, recordMetric, initWebVitals, flushLogs, initConsoleInterception, generateCorrelationId, getCorrelationId, getSessionId, logger } from './monitoring';

package/dist/sessionStorage.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Browser storage that belongs to the signed-in session rather than to the
+ * browser.
+ *
+ * localStorage is scoped per origin, so anything written here outlives a
+ * sign-out and is handed to whoever signs in next. For preferences that is
+ * fine — for anything the backend authorizes against, it is a bug: the
+ * incoming account sends the previous account's context and gets 403s it
+ * cannot explain, from a UI that looks correctly configured.
+ *
+ * `logout()` clears every key listed here. Add a key to this list rather than
+ * clearing it at the call site, so a new front or a second logout button
+ * cannot miss it.
+ */
+/** Tenant (personal vs group) context — owned by `useTenant` in @tumbaland/components. */
+export declare const TENANT_STORAGE_KEY = "selectedTenant";
+export declare function clearSessionScopedStorage(): void;

package/dist/sessionStorage.js

@@ -0,0 +1,28 @@
+import { logger } from './monitoring';
+/**
+ * Browser storage that belongs to the signed-in session rather than to the
+ * browser.
+ *
+ * localStorage is scoped per origin, so anything written here outlives a
+ * sign-out and is handed to whoever signs in next. For preferences that is
+ * fine — for anything the backend authorizes against, it is a bug: the
+ * incoming account sends the previous account's context and gets 403s it
+ * cannot explain, from a UI that looks correctly configured.
+ *
+ * `logout()` clears every key listed here. Add a key to this list rather than
+ * clearing it at the call site, so a new front or a second logout button
+ * cannot miss it.
+ */
+/** Tenant (personal vs group) context — owned by `useTenant` in @tumbaland/components. */
+export const TENANT_STORAGE_KEY = 'selectedTenant';
+const SESSION_SCOPED_KEYS = [TENANT_STORAGE_KEY];
+export function clearSessionScopedStorage() {
+    for (const key of SESSION_SCOPED_KEYS) {
+        try {
+            localStorage.removeItem(key);
+        }
+        catch (err) {
+            logger.warn('Failed to clear session-scoped storage', { key, error: err });
+        }
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tumbaland/frontend-core",
-  "version": "1.6.1",
+  "version": "1.8.0",
   "description": "Shared frontend auth/group/API-client logic for Tumbaland frontends",
   "author": "Tumbaland",
   "license": "MIT",
@@ -11,7 +11,7 @@
   ],
   "scripts": {
     "build": "tsc -p tsconfig.build.json",
-    "release": "commit-and-tag-version && npm run build && npm publish --access public",
+    "release": "commit-and-tag-version && npm run build && npm publish --access public && node ../../scripts/sync-lib-versions.mjs",
     "release:beta": "commit-and-tag-version --prerelease beta && npm run build && npm publish --access public --tag beta",
     "test": "vitest run",
     "test:coverage": "vitest run --coverage",