@flow-industries/id 0.17.0 → 0.19.0

package/dist/sdk/types/sdk.d.ts

@@ -1,6 +1,7 @@
 import type { ReactNode } from "react";
 import type { Chain, Hex, PrepareTransactionRequestParameters, SendTransactionParameters, SignTypedDataParameters, Transport, WalletClient } from "viem";
 import type { SendCallsParameters } from "viem/actions";
+import type { RawValue } from "../json";
 import type { AdditionalSession, FlowCredential, FlowUser, WebAuthnSignature } from "./auth";
 import type { ConnectCapabilities, ConnectResponse } from "./protocol";
 import type { RoomsApi } from "./rooms";
@@ -187,6 +188,11 @@ export type DialogOpenOptions = {
         icon?: string;
     };
 };
+/**
+ * Color scheme for Flow ID iframe chrome. "light dark" follows the OS, which
+ * is the default; a host with its own theme toggle passes the resolved value.
+ */
+export type ColorScheme = "light" | "dark" | "light dark";
 /** Anchor for an auto-created (host-less) profile widget container. */
 export type ProfilePosition = "top-right" | "top-left" | "bottom-right" | "bottom-left";
 export type MountProfileOptions = {
@@ -209,11 +215,17 @@ export type MountProfileOptions = {
      * Color scheme for the widget chrome. Set this to match the host (the dark
      * game UI passes "dark"). Defaults to "light dark" (follows the OS).
      */
-    theme?: "light" | "dark" | "light dark";
+    theme?: ColorScheme;
     /** Explicit Flow instance. Defaults to the createFlow() singleton. */
     flow?: Flow;
 };
 export type ProfileButtonHandle = {
+    /**
+     * Recolors the mounted pill (and its profile dialog) in place. A host with a
+     * theme toggle calls this instead of remounting: rebuilding the iframe would
+     * reload the widget and flash the pill out of the layout on every toggle.
+     */
+    setTheme: (theme: ColorScheme) => void;
     /** Tears down the iframe, listeners, and any auto-created container. */
     destroy: () => void;
 };
@@ -237,7 +249,7 @@ export type MountFlowWidgetOptions = {
      * Color scheme for the widget chrome. Set this to match the host (the dark
      * game UI passes "dark"). Defaults to "light dark" (follows the OS).
      */
-    theme?: "light" | "dark" | "light dark";
+    theme?: ColorScheme;
     /** Explicit Flow instance. Defaults to the createFlow() singleton. */
     flow?: Flow;
 };
@@ -251,7 +263,12 @@ export type FlowWidgetHandle = {
      * Sends a widget-specific message (e.g. `{ type: "xp-refresh" }`), pinned to
      * the Flow ID origin.
      */
-    post: (message: unknown) => void;
+    post: (message: RawValue) => void;
+    /**
+     * Recolors the mounted widget in place, for the same reason the pill exposes
+     * it: a remount reloads the frame and flashes it out of the host's layout.
+     */
+    setTheme: (theme: ColorScheme) => void;
     /** Tears down the iframe and its bridge. */
     destroy: () => void;
 };
@@ -263,7 +280,7 @@ export type FlowWidgetProps = {
     /** Override the Flow ID origin; defaults to the resolved Flow's `host`. */
     host?: string;
     /** Color scheme for the widget chrome; defaults to "light dark" (the OS). */
-    theme?: "light" | "dark" | "light dark";
+    theme?: ColorScheme;
 };
 export type DialogHost = {
     open: (options?: DialogOpenOptions) => void;
@@ -364,7 +381,7 @@ export type ProfileButtonProps = {
     /** Override the Flow ID origin; defaults to the resolved Flow's `host`. */
     host?: string;
     /** Color scheme for the widget chrome; defaults to "light dark" (the OS). */
-    theme?: "light" | "dark" | "light dark";
+    theme?: ColorScheme;
 };
 export type RunLoginParams = {
     dialog: DialogHost;

package/dist/sdk/types/server.d.ts

@@ -60,3 +60,21 @@ export type SessionRouteResponse = {
      */
     additionalSessions?: AdditionalSession[];
 };
+export type GracefulShutdownSignal = "SIGTERM" | "SIGINT";
+export type GracefulShutdownServer = {
+    /** Stop accepting connections; `true` also closes active connections. */
+    stop(closeActiveConnections?: boolean): Promise<void> | void;
+};
+export type GracefulShutdownOptions = {
+    /**
+     * Total time allowed for active HTTP requests and `onShutdown` to finish.
+     * Defaults to 20 seconds, leaving Kubernetes headroom around the app drain.
+     */
+    timeoutMs?: number;
+    /**
+     * Consumer cleanup started after the server stops accepting connections.
+     * Close WebSockets, flush presence, and finish other process-owned state here.
+     */
+    onShutdown?: (signal: GracefulShutdownSignal) => Promise<void> | void;
+};
+export type GracefulShutdownCleanup = () => void;

package/dist/sdk/verify.js

@@ -33,5 +33,6 @@ export async function verifyFlowJWT(token, opts) {
     });
     if (!payload.sub)
         throw new Error("JWT missing sub");
+    /* SAFETY: jwtVerify already checked the signature, issuer and audience against this issuer's own keys, and `sub` is checked above. */
     return payload;
 }

package/dist/sdk/wagmi/index.d.ts

@@ -1,3 +1,4 @@
+import type { RawValue } from "../json";
 import type { FlowConnectorParameters } from "../types";
 /**
  * Wagmi connector adapter for Flow. Drop into your wagmi config with
@@ -17,9 +18,12 @@ import type { FlowConnectorParameters } from "../types";
  * wagmi state stays in sync when login/logout happens via the SDK rather
  * than through wagmi's own `connect()`.
  */
-export declare function flowConnector(parameters?: FlowConnectorParameters): import("@wagmi/core").CreateConnectorFn<{
-    request: (...args: unknown[]) => Promise<unknown>;
-}, Record<string, unknown>, Record<string, unknown>>;
+/** The minimal EIP-1193 surface wagmi needs from this connector. */
+type FlowProvider = {
+    request: (...args: RawValue[]) => Promise<RawValue>;
+};
+export declare function flowConnector(parameters?: FlowConnectorParameters): import("@wagmi/core").CreateConnectorFn<FlowProvider, Record<string, unknown>, Record<string, unknown>>;
 export declare namespace flowConnector {
     var type: "flow";
 }
+export {};

package/dist/sdk/wagmi/index.js

@@ -5,33 +5,14 @@ flowConnector.type = "flow";
 function loginOptionsFromCapabilities(capabilities) {
     const signUp = capabilities?.type === "sign-up" || capabilities?.createAccount;
     const signIn = capabilities?.type === "sign-in" || capabilities?.signIn;
+    const headless = !signUp &&
+        (capabilities?.signInHeadless || capabilities?.type === "sign-in");
     return {
-        ...(signUp ? { signUp: true } : {}),
-        ...(!signUp && signIn ? { signIn: true } : {}),
-        ...(!signUp &&
-            (capabilities?.signInHeadless || capabilities?.type === "sign-in")
-            ? { signInHeadless: true }
-            : {}),
+        signUp: signUp ? true : undefined,
+        signIn: !signUp && signIn ? true : undefined,
+        signInHeadless: headless ? true : undefined,
     };
 }
-/**
- * Wagmi connector adapter for Flow. Drop into your wagmi config with
- * `connectors: [flowConnector()]` — no arguments needed in the common case.
- *
- * Resolution order for the underlying Flow instance:
- *  1. `parameters.flow` (explicit override — useful for tests)
- *  2. The Flow singleton set by a prior `createFlow()` call
- *  3. Lazily created on first connector use (also sets the singleton)
- *
- * This means wagmi-only apps get a working Flow without ever calling
- * `createFlow`, and apps mixing wagmi + direct SDK calls automatically
- * share state because they all resolve to the same singleton.
- *
- * The `setup()` method subscribes to the Flow store and emits wagmi
- * `connect`/`disconnect` events whenever the address changes — that's how
- * wagmi state stays in sync when login/logout happens via the SDK rather
- * than through wagmi's own `connect()`.
- */
 export function flowConnector(parameters = {}) {
     let flow = parameters.flow ?? null;
     return createConnector((config) => {
@@ -64,6 +45,8 @@ export function flowConnector(parameters = {}) {
                         return;
                     lastAddress = next;
                     if (next) {
+                        /* SAFETY: wagmi types `accounts` as a readonly tuple of its own `Address` brand;
+                           `next` is the checksummed address this connector just resolved. */
                         config.emitter.emit("connect", {
                             accounts: [next],
                             chainId: config.chains[0]?.id ?? 1,
@@ -76,6 +59,7 @@ export function flowConnector(parameters = {}) {
             },
             async connect(params = {}) {
                 const f = getFlow();
+                // SAFETY: wagmi passes its own connect options; WagmiConnectParams names the subset read.
                 const connectParams = params;
                 const isReconnecting = connectParams.isReconnecting;
                 // Wagmi calls connect({ isReconnecting: true }) on mount when it
@@ -135,15 +119,18 @@ export function flowConnector(parameters = {}) {
             },
             async getClient({ chainId } = {}) {
                 const f = getFlow();
-                return f.walletClient({ ...(chainId ? { chainId } : {}) });
+                /* SAFETY: wagmi types getClient against viem's Client generic over its own chain
+                   config; the Flow wallet client implements that surface. */
+                return f.walletClient(chainId ? { chainId } : {});
             },
-            async getProvider({ chainId } = {}) {
-                const client = await this.getClient({
-                    ...(chainId ? { chainId } : {}),
-                });
-                return {
-                    request: client.request,
-                };
+            async getProvider(options = {}) {
+                const client = await this.getClient?.({ chainId: options.chainId });
+                /* SAFETY: the wallet client viem builds always carries `request`; wagmi's Client type
+                   does not name it, which is the only reason this is stated rather than inferred. */
+                const request = Object.entries(Object(client)).find(([k]) => k === "request")?.[1];
+                /* SAFETY: the wallet client viem builds always carries `request`; wagmi's Client type
+                   does not name it, which is the only reason this is read by name. */
+                return { request: request };
             },
             onAccountsChanged() { },
             onChainChanged(chain) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flow-industries/id",
-  "version": "0.17.0",
+  "version": "0.19.0",
   "main": "./dist/sdk/client/index.js",
   "module": "./dist/sdk/client/index.js",
   "types": "./dist/sdk/client/index.d.ts",
@@ -47,10 +47,7 @@
     "dist/sdk"
   ],
   "scripts": {
-    "dev": "bunx vite & bunx vite --config vite.playground.config.ts & bunx vite --config vite.landing.config.ts & bun run --watch src/index.ts",
-    "dev:dialog": "bunx vite",
-    "dev:playground": "bunx vite --config vite.playground.config.ts",
-    "dev:landing": "bunx vite --config vite.landing.config.ts",
+    "dev": "./dev.sh",
     "build:dialog": "bunx vite build",
     "build:playground": "bunx vite build --config vite.playground.config.ts",
     "build:landing": "bunx vite build --config vite.landing.config.ts",
@@ -59,12 +56,12 @@
     "prepublishOnly": "bun run build:sdk",
     "start": "bun run src/index.ts",
     "worker": "bun run src/worker.ts",
-    "email:dev": "email dev --dir src/emails --port 3010",
     "db:generate": "bunx @better-auth/cli generate",
     "db:migrate:gen": "bunx drizzle-kit generate",
     "db:migrate": "bunx drizzle-kit migrate",
     "db:push": "bunx drizzle-kit push",
     "db:studio": "bunx drizzle-kit studio",
+    "usernames:refresh": "bun run scripts/generate-reserved-usernames.ts",
     "lint": "biome check",
     "test": "bun test src",
     "format": "biome format --write",
@@ -91,9 +88,9 @@
   },
   "devDependencies": {
     "@better-auth/cli": "^1.4.17",
-    "@biomejs/biome": "2.4.12",
+    "@biomejs/biome": "2.5.8",
     "@electric-sql/pglite": "^0.5.4",
-    "@flow-industries/lint": "0.1.0",
+    "@flow-industries/lint": "0.3.0",
     "@react-email/ui": "^6.6.0",
     "@tailwindcss/vite": "^4.1.18",
     "@tanstack/react-router-devtools": "^1.160.0",
@@ -104,6 +101,7 @@
     "@types/react": "^19.2.13",
     "@types/react-dom": "^19.2.3",
     "@vitejs/plugin-react": "^5.1.3",
+    "biome-anti-slop": "0.1.0",
     "drizzle-kit": "^0.31.8",
     "pino-pretty": "^13.1.3",
     "react-email": "^6.6.0",
@@ -112,6 +110,10 @@
     "typescript": "^5",
     "vite": "^7.3.1"
   },
+  "trustedDependencies": [
+    "esbuild",
+    "sharp"
+  ],
   "dependencies": {
     "@aws-sdk/client-s3": "^3.1073.0",
     "@flow-industries/ui": "^0.19.0",
@@ -146,6 +148,7 @@
     "tempo.ts": "^0.14.2",
     "viem": "2.47.10",
     "wagmi": "^3.4.2",
+    "zod": "^4.3.6",
     "zustand": "^5.0.11"
   }
 }

package/dist/sdk/client/refresh-store.d.ts

@@ -1,22 +0,0 @@
-import type { RefreshCookieConfig } from "../types";
-/**
- * First-party persistence for the rotating refresh token. It lives in the
- * consumer app's OWN localStorage (origin-scoped), so it survives reloads and
- * navigations and — unlike the old id.flow.industries cookie — is never a
- * third-party cookie, so iOS ITP can't block it. Keyed by `host` so pointing
- * the SDK at a different Flow ID origin (dev vs prod) doesn't collide.
- */
-export interface RefreshStore {
-    get(): string | null;
-    set(token: string): void;
-    clear(): void;
-}
-/**
- * With a cookie config (`createFlow({ cookies: true })`) the token is
- * additionally mirrored into a first-party cookie so the app's own server can
- * refresh the session during SSR. Reads prefer the cookie: the only writer
- * that updates one side without the other is that server (Set-Cookie only),
- * and its value is always a successor of whatever localStorage still holds;
- * every client-side write hits both in the same call.
- */
-export declare function makeRefreshStore(host: string, cookie?: RefreshCookieConfig): RefreshStore;

package/dist/sdk/client/refresh-store.js

@@ -1,66 +0,0 @@
-import { clearBrowserCookie, REFRESH_COOKIE_MAX_AGE_S, readBrowserCookie, writeBrowserCookie, } from "../cookies";
-/**
- * With a cookie config (`createFlow({ cookies: true })`) the token is
- * additionally mirrored into a first-party cookie so the app's own server can
- * refresh the session during SSR. Reads prefer the cookie: the only writer
- * that updates one side without the other is that server (Set-Cookie only),
- * and its value is always a successor of whatever localStorage still holds;
- * every client-side write hits both in the same call.
- */
-export function makeRefreshStore(host, cookie) {
-    const key = `flow.id.refresh:${host}`;
-    const readLocal = () => {
-        try {
-            return localStorage.getItem(key);
-        }
-        catch {
-            return null;
-        }
-    };
-    const readCookie = () => {
-        if (!cookie || typeof document === "undefined")
-            return null;
-        return readBrowserCookie(document.cookie, cookie.name);
-    };
-    const store = {
-        get() {
-            return readCookie() ?? readLocal();
-        },
-        set(token) {
-            // Never persist a missing token: localStorage.setItem coerces undefined
-            // to the literal "undefined", which later reads back as a bogus bearer
-            // and 401s as refresh_token_invalid. Fail safe by ignoring it instead.
-            if (!token)
-                return;
-            try {
-                localStorage.setItem(key, token);
-            }
-            catch { }
-            if (cookie) {
-                writeBrowserCookie(cookie.name, token, {
-                    maxAge: REFRESH_COOKIE_MAX_AGE_S,
-                    secure: cookie.secure,
-                });
-            }
-        },
-        clear() {
-            try {
-                localStorage.removeItem(key);
-            }
-            catch { }
-            if (cookie)
-                clearBrowserCookie(cookie.name, { secure: cookie.secure });
-        },
-    };
-    // One-time reconcile so exactly one canonical value exists before the first
-    // refresh: an SSR rotation updates only the cookie, leaving localStorage one
-    // generation behind — presenting that stale token would look like reuse.
-    const fromCookie = readCookie();
-    if (fromCookie && fromCookie !== readLocal()) {
-        try {
-            localStorage.setItem(key, fromCookie);
-        }
-        catch { }
-    }
-    return store;
-}