@cosmoops/connect-sdk 0.3.0 → 0.6.0

package/dist/esm/client/index.js

@@ -11,7 +11,7 @@
  * whatever theme the host service platform already configured, and one theme
  * change lands identically in all of them.
  */
-export { ConnectProvider, useConnect, useConnectUser, useConnectEntitlements, useConnectPlans, useConnectApps, useConnectAddonUsage, useConnectSessions, useConnectResource, CONNECT_APP_URL, } from "./provider.js";
+export { ConnectProvider, useConnect, useConnectUser, useConnectEntitlements, useConnectPlans, useConnectApps, useConnectAddonUsage, useConnectSessions, useConnectIntegrations, useConnectResource, CONNECT_APP_URL, } from "./provider.js";
 // Re-exported from the root entry rather than kept there alone: it is a pure
 // helper, but every caller is UI code, and making a component file reach two
 // entry points for one function is friction with nothing behind it.
@@ -24,7 +24,20 @@ export { ConnectUserMenu, ConnectManageSubscriptionButton, ConnectInvoicesButton
 // Built, compiled into `dist/`, and reachable from no entry point until now -
 // `ConnectUserMenu` was the only thing that could render it.
 export { ConnectAccountSessions } from "./components/account-sessions.js";
+// The frame the rest of these components live inside. Exported next to the
+// pieces it composes rather than in a section of its own - an integration
+// reaching for a sidebar wants to find the launcher and the account menu in
+// the same breath, since the shell already mounts both.
+export { ConnectAppShell } from "./components/app-shell.js";
+export { ConnectSideNav } from "./components/side-nav.js";
+export { useActivePath } from "./use-active-path.js";
+// The nav model is plain data and pure functions - a host generating its nav
+// from its own route table needs the types, and `resolveActivePath` is the
+// same longest-prefix rule the sidebar highlights with, so a breadcrumb or a
+// page title derived from it cannot disagree with the rail.
+export { normalizeNav, flattenNav, normalizePath, resolveActivePath, isNavItemActive, gateExemptPaths, } from "./components/nav.js";
 export { ConnectAppsGrid } from "./components/apps-grid.js";
+export { ConnectIntegrationsModal } from "./components/integrations-modal.js";
 export { ConnectPlans } from "./components/plans.js";
 export { ConnectSubscribeDialog } from "./components/subscribe-dialog.js";
 // The subscribe / upgrade / downgrade flow's two moving parts, exported so a
@@ -34,6 +47,7 @@ export { ConnectSubscribeDialog } from "./components/subscribe-dialog.js";
 // Subscription state, gates and the surfaces around the plan grid.
 export { ConnectSubscriptionGate, ConnectNoSubscriptionCard, ConnectSubscriptionCard, ConnectTrialBanner, ConnectSeatUsage, resolveSubscriptionState, } from "./components/subscription.js";
 export { ConnectReadinessBanner, ConnectReadinessGate } from "./components/readiness.js";
+export { ConnectAccessGate, useConnectAccessGate } from "./components/access-gate.js";
 export { ConnectFeatureGate, useConnectFeature } from "./components/feature-gate.js";
 export { ConnectUsageMeter } from "./components/usage-meter.js";
 export { ConnectPlansPage } from "./components/plans-page.js";

package/dist/esm/client/provider.js

@@ -3,6 +3,8 @@ import { jsx as _jsx } from "react/jsx-runtime";
 import { createContext, useCallback, useContext, useEffect, useMemo, useRef, useState } from "react";
 export const CONNECT_APP_URL = "https://connect.cosmoops.com";
 const ConnectContext = createContext(null);
+/** Marks that this tab has already spent its one silent attempt - see `ConnectProviderProps.silentSignIn`. */
+const SILENT_ATTEMPT_KEY = "connect_silent_attempted";
 /**
  * Wraps the part of your app that shows Connect UI.
  *
@@ -17,14 +19,44 @@ const ConnectContext = createContext(null);
  * </ConnectProvider>
  * ```
  */
-export function ConnectProvider({ clientId = "", basePath = "/api/connect", redirectUri, appUrl = CONNECT_APP_URL, fetch: fetchImpl, children, }) {
+export function ConnectProvider({ clientId = "", basePath = "/api/connect", redirectUri, appUrl = CONNECT_APP_URL, fetch: fetchImpl, silentSignIn = false, children, }) {
     // One state cell, not three. `isLoading` is *derived* from "no result yet"
     // rather than set - a `setIsLoading(true)` at the top of an effect is a
     // synchronous setState inside that effect, which cascades an extra render
     // and is what `react-hooks/set-state-in-effect` flags. Everything below
     // writes state only from an async callback.
     const [result, setResult] = useState(null);
-    const isLoading = result === null;
+    /**
+     * Whether this tab has already spent its one silent attempt, sampled once
+     * at mount.
+     *
+     * A lazy `useState` initializer rather than a read inside the render body:
+     * `sessionStorage` is external mutable state, and reading it during render
+     * is impure - with the React Compiler on, that is exactly the kind of thing
+     * that can be hoisted or memoized into the wrong answer. An initializer
+     * runs once, which is all this needs; the value only ever changes as this
+     * component navigates the page away.
+     *
+     * Safe on the server, where it reads `false`: `result` is `null` during SSR
+     * and first client render alike, so `isLoading` below is `true` on both
+     * regardless of this value, and hydration cannot diverge on it.
+     */
+    const [silentAttemptSpent] = useState(() => typeof window !== "undefined" && window.sessionStorage.getItem(SILENT_ATTEMPT_KEY) === "1");
+    /**
+     * A silent attempt is settled-signed-out *and* about to redirect. Reported
+     * as still-loading, which is the honest answer: the question "is this
+     * visitor signed in" has not been finally answered yet, and there is a
+     * navigation already on its way.
+     *
+     * Without this the provider publishes `signed out` for the one frame before
+     * the effect below fires, so every consumer paints its signed-out state -
+     * a "Sign in" button, the plan-picker gate - and then the page vanishes
+     * underneath it. Flashing a sales pitch at someone who is about to be
+     * silently signed in is the same bug `ConnectSubscriptionGate` exists to
+     * prevent, one layer down.
+     */
+    const silentPending = silentSignIn && !silentAttemptSpent && result !== null && !result.session.user && !result.error;
+    const isLoading = result === null || silentPending;
     const session = result?.session ?? null;
     const error = result?.error ?? null;
     // One entry per path. Held in a ref, not state, because a cache write must
@@ -104,6 +136,21 @@ export function ConnectProvider({ clientId = "", basePath = "/api/connect", redi
         // eslint-disable-next-line react-hooks/set-state-in-effect
         void refresh();
     }, [refresh]);
+    useEffect(() => {
+        // `silentPending` already encodes settled-and-signed-out, no prior
+        // attempt, and no bridge error - a failed bridge read says nothing about
+        // whether Connect has a session, and bouncing the browser on a transient
+        // network failure would turn a recoverable error into a navigation nobody
+        // asked for.
+        if (!silentPending || typeof window === "undefined")
+            return;
+        // Written before navigating, not after: a navigation that begins before
+        // the marker lands leaves the tab unmarked and free to probe again on the
+        // way back, which is the loop this bounds.
+        window.sessionStorage.setItem(SILENT_ATTEMPT_KEY, "1");
+        const next = `${window.location.pathname}${window.location.search}`;
+        window.location.href = `${basePath}/signin?prompt=none&next=${encodeURIComponent(next)}`;
+    }, [silentPending, basePath]);
     const signIn = useCallback((options = {}) => {
         const url = new URL("/sso/authorize", appUrl);
         url.searchParams.set("client_id", clientId);
@@ -186,6 +233,10 @@ export function useConnectPlans() {
 export function useConnectApps() {
     return useConnectResource("/apps");
 }
+/** Enabled Composio-hosted toolkits and this organization's connection status for each. */
+export function useConnectIntegrations() {
+    return useConnectResource("/integrations");
+}
 /**
  * This Connect account's own login sessions - account-wide, not scoped to
  * this service, see `SessionsListResponse`'s doc comment. The component

package/dist/esm/client/use-active-path.js

@@ -0,0 +1,74 @@
+"use client";
+import { useSyncExternalStore } from "react";
+const LOCATION_CHANGE = "connect:locationchange";
+let patched = false;
+/**
+ * Make `history.pushState`/`replaceState` announce themselves.
+ *
+ * Neither fires an event - `popstate` covers Back and Forward only - so a
+ * client-side router that pushes a new URL moves the address bar and tells
+ * nothing outside itself. Without this, a sidebar reading `location.pathname`
+ * highlights whatever route the page first loaded on and then never moves
+ * again.
+ *
+ * Both wrappers call through to the original first and return its result, so
+ * the patch is transparent to whatever router installed the navigation; it is
+ * applied at most once per document, and only when a `ConnectSideNav` is
+ * actually mounted without an `activePath`. Pass `activePath` (Next:
+ * `usePathname()`) and none of this runs at all - which is the recommended
+ * path for any app that has a router to ask.
+ */
+function patchHistory() {
+    if (patched || typeof window === "undefined" || typeof window.history === "undefined")
+        return;
+    patched = true;
+    for (const method of ["pushState", "replaceState"]) {
+        const original = window.history[method];
+        window.history[method] = function patchedHistoryMethod(...args) {
+            const result = original.apply(this, args);
+            window.dispatchEvent(new Event(LOCATION_CHANGE));
+            return result;
+        };
+    }
+}
+function subscribe(onStoreChange) {
+    patchHistory();
+    window.addEventListener("popstate", onStoreChange);
+    window.addEventListener(LOCATION_CHANGE, onStoreChange);
+    return () => {
+        window.removeEventListener("popstate", onStoreChange);
+        window.removeEventListener(LOCATION_CHANGE, onStoreChange);
+    };
+}
+function getSnapshot() {
+    return window.location.pathname;
+}
+/**
+ * The server never has a location, and guessing one is worse than having
+ * none: a guess that misses renders a *different* item highlighted on the
+ * server than on the client, which is a hydration mismatch. `""` matches no
+ * nav item, so the first paint has no highlight and the client's first commit
+ * adds it.
+ *
+ * Doubles as the snapshot when `activePath` *was* supplied - the value is
+ * discarded either way, and pairing it with `noopSubscribe` is what keeps a
+ * controlled shell from ever touching `history` or `window.location`.
+ */
+function emptySnapshot() {
+    return "";
+}
+function noopSubscribe() {
+    return () => { };
+}
+/**
+ * The current path, from `activePath` when given and from the browser
+ * otherwise.
+ *
+ * Exported because a host building its own shell out of `ConnectSideNav`
+ * needs the same fallback the shell uses.
+ */
+export function useActivePath(activePath) {
+    const controlled = activePath !== undefined;
+    const live = useSyncExternalStore(controlled ? noopSubscribe : subscribe, controlled ? emptySnapshot : getSnapshot, emptySnapshot);
+    return activePath ?? live;
+}

package/dist/esm/errors.js

@@ -55,7 +55,7 @@ export class ConnectError extends Error {
      * guessing keys. These two are the exception: reaching them required
      * presenting a key whose hash matched, so you already hold it, and what you
      * need to know is that no retry and no scope change will fix this - the key
-     * has to be reissued from the service's Setup tab.
+     * has to be reissued from the service's Integration tab.
      *
      * Worth alerting on. It is the one failure that will not resolve itself and
      * takes down every call your integration makes.

package/dist/esm/next/index.js

@@ -1,13 +1,18 @@
+import { cache } from "react";
 import { ConnectClient } from "../server/client.js";
 import { createConnectHandler } from "../server/handler.js";
 /**
  * Plug-and-play wiring for Next.js.
  *
  * Everything below is server-side. Nothing here is *statically* imported from
- * `next`, so this module loads in App Router route handlers, the Node runtime
- * and the edge runtime alike - and needs no peer dependency. The one place
- * that does reach for `next/headers` does it behind a dynamic import, inside
- * the function that needs it, and says so when it isn't there.
+ * `next` itself, so this module loads in App Router route handlers, the Node
+ * runtime and the edge runtime alike without a `next` peer dependency. The
+ * one place that does reach for `next/headers` (or, in `requireConnectSession`,
+ * `next/navigation`) does it behind a dynamic import, inside the function that
+ * needs it, and says so when it isn't there. `react` is a real, static
+ * dependency though - `getConnectSession`'s automatic per-request memoization
+ * (below) is built on its `cache()`, which every App Router project already
+ * has.
  *
  * The whole integration is two files:
  *
@@ -33,7 +38,7 @@ import { createConnectHandler } from "../server/handler.js";
  * | `CONNECT_SESSION_COOKIE` | no | session cookie name |
  *
  * Register `{your origin}/api/connect/callback` as a redirect URI in the
- * service's Setup tab. That is the only step this cannot do for you.
+ * service's Integration tab. That is the only step this cannot do for you.
  *
  * No `next.config.ts` changes needed either, including `transpilePackages`:
  * `dist/` is already ES2022 with `"use client"` hoisted to the top of every
@@ -198,6 +203,35 @@ async function requestFromHeaders() {
     const proto = incoming.get("x-forwarded-proto") ?? (host.startsWith("localhost") ? "http" : "https");
     return new Request(`${proto}://${host}/`, { headers: incoming });
 }
+async function readSession(request, options) {
+    const store = options.session ?? cookieSessionStore();
+    const token = await store.read(request);
+    if (!token)
+        return null;
+    try {
+        return await (options.client ?? connectClient()).identity.getUser(token);
+    }
+    catch {
+        return null;
+    }
+}
+/**
+ * The ambient case - no explicit `request`, default client, default cookie
+ * store - wrapped in React's `cache()` so every call in the same request
+ * shares one round trip to Connect. A layout reading the session for a nav
+ * avatar and the page beneath it reading it again for a role check hit this
+ * exact function; without the wrapper that's two live reads of the same
+ * answer.
+ *
+ * Deliberately its own zero-argument function rather than `cache()` wrapping
+ * `getConnectSession` directly - `cache()` keys on argument identity, and
+ * `getConnectSession`'s default `options = {}` is a fresh object on every
+ * call, so wrapping it as-is would never hit the cache for the very call
+ * pattern this exists to speed up.
+ */
+const cachedAmbientSession = cache(async () => {
+    return readSession(await requestFromHeaders(), {});
+});
 /**
  * The signed-in user for a Server Component, Route Handler or Server Action,
  * or `null`.
@@ -208,6 +242,9 @@ async function requestFromHeaders() {
  * if (!session) redirect("/api/connect/signin?next=/dashboard");
  * ```
  *
+ * `requireConnectSession()` below is that exact check in one call, for the
+ * common case of "redirect if signed out."
+ *
  * Pass a `Request` to use it somewhere `next/headers` does not exist - a
  * framework-agnostic handler, a test, a custom server. Both forms take the
  * same path afterwards; the argument is only how the cookie is found.
@@ -219,18 +256,61 @@ async function requestFromHeaders() {
  *
  * Returns `null` for every failure - an expired session and a missing one both
  * mean "not signed in", and a page guard should not need a try/catch.
+ *
+ * **Memoized per request for the plain, zero-argument call** - the shape
+ * every page, layout and Server Action actually uses - via React's `cache()`.
+ * Passing an explicit `request`, `client` or `session` bypasses the cache
+ * and always makes a live call: those are for tests and non-ambient
+ * callers, where a fresh read every time is the point, not an oversight.
  */
 export async function getConnectSession(request, options = {}) {
-    const store = options.session ?? cookieSessionStore();
-    const token = await store.read(request ?? (await requestFromHeaders()));
-    if (!token)
-        return null;
-    try {
-        return await (options.client ?? connectClient()).identity.getUser(token);
-    }
-    catch {
-        return null;
-    }
+    if (!request && !options.client && !options.session)
+        return cachedAmbientSession();
+    return readSession(request ?? (await requestFromHeaders()), options);
+}
+/**
+ * `getConnectSession()`, minus the boilerplate of checking it and redirecting
+ * yourself:
+ *
+ * ```tsx
+ * // app/dashboard/page.tsx
+ * const session = await requireConnectSession();
+ * ```
+ *
+ * Redirects to `/signin` under the same `basePath` as `getConnectSession`'s
+ * default (`/api/connect`) when signed out - pass `signInPath` if you mounted
+ * the bridge somewhere else, and `next` to send the visitor back to where
+ * they were once they're signed in. Only sensible in a Server Component,
+ * Route Handler or Server Action, the same three places `redirect()` from
+ * `next/navigation` itself works.
+ *
+ * A thin wrapper, not a framework of its own - reach for `getConnectSession`
+ * plus your own check when "not signed in" isn't "redirect to sign-in"
+ * (an API route returning 401, say). Role and entitlement checks stay
+ * outside this function on purpose: `session.serviceRole.granted` and
+ * `connect.entitlements.*` are one line each on top of the session this
+ * already gives you, and where that line redirects (a plans page, a
+ * "forbidden" screen) is a decision only your app can make - see
+ * "Authentication & authorization" for the pattern.
+ */
+export async function requireConnectSession(request, options = {}) {
+    const session = await getConnectSession(request, options);
+    if (session)
+        return session;
+    const signIn = options.signInPath ?? "/api/connect/signin";
+    return redirectTo(options.next ? `${signIn}?next=${encodeURIComponent(options.next)}` : signIn);
+}
+/**
+ * `next/navigation`'s `redirect()`, imported the same dynamic way as
+ * `next/headers` above and for the same reason: no static dependency on
+ * `next`'s own types at this package's build time. Typed by hand rather than
+ * imported, since that's the only way to erase them - `redirect()` itself is
+ * typed `never`, which is what lets `requireConnectSession` return here
+ * without its own `return` after the call.
+ */
+async function redirectTo(url) {
+    const { redirect } = (await import("next/navigation"));
+    return redirect(url);
 }
 export { createConnectHandler } from "../server/handler.js";
 export { ConnectClient } from "../server/client.js";

package/dist/esm/server/client.js

@@ -5,7 +5,9 @@ import { BillingResource } from "./resources/billing.js";
 import { DriveResource } from "./resources/drive.js";
 import { EntitlementsResource } from "./resources/entitlements.js";
 import { IdentityResource } from "./resources/identity.js";
+import { IntegrationsResource } from "./resources/integrations.js";
 import { LogsResource } from "./resources/logs.js";
+import { AnalyticsResource } from "./resources/analytics.js";
 import { OtpResource } from "./resources/otp.js";
 import { SessionsResource } from "./resources/sessions.js";
 export const DEFAULT_BASE_URL = "https://connect.cosmoops.com";
@@ -76,12 +78,16 @@ export class ConnectClient {
     otp;
     /** Feature events into the Console's audit log, filterable to your service. */
     logs;
+    /** Emit product events and read back this service's aggregated numbers. */
+    analytics;
     /** This Connect account's own login sessions - account-wide, not scoped to this service. Requires the `sessions:manage` scope. */
     sessions;
+    /** Composio-hosted third-party connections (Google Calendar, Slack, ...) an organization has connected. */
+    integrations;
     constructor(options) {
         assertNotBrowser();
         if (!options.apiKey) {
-            throw new TypeError("ConnectClient requires `apiKey` - the plaintext shown once in the Setup tab.");
+            throw new TypeError("ConnectClient requires `apiKey` - the plaintext shown once in the Integration tab.");
         }
         const appBaseUrl = (options.baseUrl ?? DEFAULT_BASE_URL).replace(/\/+$/, "");
         const transport = {
@@ -103,8 +109,10 @@ export class ConnectClient {
         this.ai = new AiResource(transport);
         this.otp = new OtpResource(transport);
         this.logs = new LogsResource(transport);
+        this.analytics = new AnalyticsResource(transport);
         this.sessions = new SessionsResource(transport, options.clientId ?? null);
+        this.integrations = new IntegrationsResource(transport);
     }
 }
 /** Kept in step with `package.json` by `sdk.test.ts`. */
-export const SDK_VERSION = "0.3.0";
+export const SDK_VERSION = "0.6.0";

package/dist/esm/server/handler.js

@@ -101,6 +101,7 @@ export function createConnectHandler(options) {
     const { client, session } = options;
     const defaultRedirect = options.defaultRedirect ?? "/";
     const stateCookieName = options.stateCookieName ?? "connect_oauth_state";
+    const silentCookieName = `${stateCookieName}_silent`;
     const callbackPath = `${basePath}/callback`;
     /**
      * Short-lived, httpOnly, and `SameSite=Lax` - `Strict` would not be sent on
@@ -121,6 +122,32 @@ export function createConnectHandler(options) {
             .filter(Boolean)
             .join("; ");
     }
+    /**
+     * Marks the in-flight round trip as a silent (`prompt=none`) one, so the
+     * callback can tell a *probe that found nobody* from a *sign-in that
+     * failed*. The two arrive as the identical `error=login_required`, and they
+     * need opposite handling - see the callback.
+     *
+     * A cookie of its own rather than a flag folded into the state cookie:
+     * that one is parsed by splitting on `:` with the destination URL rejoined
+     * from the remainder, so smuggling a third field through it is exactly the
+     * kind of encoding trick that breaks the first time a `next` URL contains
+     * something unexpected. Same attributes and lifetime as the state cookie
+     * it travels beside.
+     */
+    function silentCookie(value, secure) {
+        const cleared = value === "";
+        return [
+            `${silentCookieName}=${encodeURIComponent(value)}`,
+            `Path=${basePath}`,
+            "HttpOnly",
+            "SameSite=Lax",
+            secure ? "Secure" : "",
+            cleared ? "Max-Age=0" : "Max-Age=900",
+        ]
+            .filter(Boolean)
+            .join("; ");
+    }
     async function requireToken(request) {
         const token = await session.read(request);
         if (!token) {
@@ -166,6 +193,37 @@ export function createConnectHandler(options) {
             const { user } = await whoami(request);
             return json({ apps: await client.apps.list(user.organizationId) });
         },
+        "GET /integrations": async (request) => {
+            const { user } = await whoami(request);
+            return json({ toolkits: await client.integrations.list(user.organizationId) });
+        },
+        "POST /integrations/connect": async (request) => {
+            const { user } = await whoami(request);
+            const body = (await request.json().catch(() => null));
+            if (!body?.toolkitSlug || !body?.returnUrl) {
+                throw new ConnectError({
+                    status: 400,
+                    code: "validation_error",
+                    message: "toolkitSlug and returnUrl are required",
+                    endpoint: "POST /integrations/connect",
+                });
+            }
+            return json(await client.integrations.initiateConnect(user.organizationId, body.toolkitSlug, body.returnUrl));
+        },
+        "POST /integrations/disconnect": async (request) => {
+            const { user } = await whoami(request);
+            const body = (await request.json().catch(() => null));
+            if (!body?.toolkitSlug) {
+                throw new ConnectError({
+                    status: 400,
+                    code: "validation_error",
+                    message: "toolkitSlug is required",
+                    endpoint: "POST /integrations/disconnect",
+                });
+            }
+            await client.integrations.disconnect(user.organizationId, body.toolkitSlug);
+            return json({ ok: true });
+        },
         // Account-wide, not scoped to this service - see `SessionsResource`'s
         // doc comment. `requireToken` alone identifies the caller; the target
         // `sessionId` on the revoke routes travels in the JSON body, not the
@@ -205,14 +263,19 @@ export function createConnectHandler(options) {
             const secure = url.protocol === "https:";
             const state = createState();
             const next = safeRedirect(url.searchParams.get("next"), defaultRedirect);
+            const requestedPrompt = url.searchParams.get("prompt");
+            const prompt = requestedPrompt === "create" || requestedPrompt === "none" ? requestedPrompt : undefined;
             const authorizeUrl = client.identity.authorizeUrl({
                 redirectUri: `${url.origin}${callbackPath}`,
                 state,
-                ...(url.searchParams.get("prompt") === "create" ? { prompt: "create" } : {}),
+                ...(prompt ? { prompt } : {}),
             });
             // State and destination travel together in one cookie so the callback
             // cannot end up with one and not the other.
-            return redirect(authorizeUrl, [stateCookie(`${state}:${next}`, secure)]);
+            const cookies = [stateCookie(`${state}:${next}`, secure)];
+            if (prompt === "none")
+                cookies.push(silentCookie("1", secure));
+            return redirect(authorizeUrl, cookies);
         },
         /**
          * The other end of the round trip. Verifies `state`, exchanges the code,
@@ -229,10 +292,29 @@ export function createConnectHandler(options) {
             if (!cookieState || !sameState(cookieState, returnedState)) {
                 // Either a forged callback or a genuinely stale tab. Neither should
                 // mint a session, and neither is worth an error page.
-                return redirect(`${next}${next.includes("?") ? "&" : "?"}connect_error=state_mismatch`, [clearState]);
+                return redirect(`${next}${next.includes("?") ? "&" : "?"}connect_error=state_mismatch`, [
+                    clearState,
+                    silentCookie("", secure),
+                ]);
             }
+            const wasSilent = readCookie(request, silentCookieName) === "1";
+            const clearSilent = silentCookie("", secure);
             const error = url.searchParams.get("error");
             if (error) {
+                // A silent (`prompt=none`) probe that came back empty-handed. All
+                // three of its outcomes mean the same thing to the app - "carry on
+                // signed out" - so it returns to `next` quietly: no retry, and no
+                // `connect_error`, because nothing went wrong.
+                //
+                // Getting this wrong is not subtle. The retry below fires on exactly
+                // the `login_required` a silent probe returns, so without this branch
+                // every silent attempt for a signed-out visitor would escalate itself
+                // into a full interactive sign-in redirect - turning "quietly check
+                // if they're already here" into "force everyone to log in", which is
+                // the precise opposite of the feature.
+                if (wasSilent) {
+                    return redirect(next, [clearState, clearSilent]);
+                }
                 // `login_required` is normal traffic, not a fault: a new account gets
                 // pulled out to their inbox to verify, and the ~15 minute request
                 // expires before they return. Connect has already signed them in, so
@@ -242,15 +324,16 @@ export function createConnectHandler(options) {
                     const retry = new URL(`${url.origin}${basePath}/signin`);
                     retry.searchParams.set("next", next);
                     retry.searchParams.set("connect_retry", "1");
-                    return redirect(retry.toString(), [clearState]);
+                    return redirect(retry.toString(), [clearState, clearSilent]);
                 }
                 return redirect(`${next}${next.includes("?") ? "&" : "?"}connect_error=${encodeURIComponent(error)}`, [
                     clearState,
+                    clearSilent,
                 ]);
             }
             const code = url.searchParams.get("code");
             if (!code) {
-                return redirect(`${next}${next.includes("?") ? "&" : "?"}connect_error=missing_code`, [clearState]);
+                return redirect(`${next}${next.includes("?") ? "&" : "?"}connect_error=missing_code`, [clearState, clearSilent]);
             }
             const result = await client.identity.exchangeCode({
                 code,
@@ -259,7 +342,7 @@ export function createConnectHandler(options) {
             // Verified before the session is stored, not after - an unverifiable
             // token must never become a signed-in user.
             await client.identity.verifyIdToken(result.idToken);
-            const response = redirect(next, [clearState]);
+            const response = redirect(next, [clearState, clearSilent]);
             await session.write(request, response, result.sessionToken);
             return response;
         },

package/dist/esm/server/index.js

@@ -8,3 +8,8 @@
 export { ConnectClient, DEFAULT_BASE_URL, SDK_VERSION } from "./client.js";
 export { createConnectHandler } from "./handler.js";
 export { createState } from "./resources/identity.js";
+/**
+ * Webhook verification and a ready-made POST route. Server-only for the
+ * obvious reason: the signing secret must never reach a browser bundle.
+ */
+export { createConnectWebhookHandler, verifyConnectWebhook, } from "./webhooks.js";

package/dist/esm/server/resources/analytics.js

@@ -0,0 +1,62 @@
+import { request } from "../http.js";
+/**
+ * Your service's own analytics: emit product events, and read back the daily
+ * numbers Connect aggregates from them.
+ *
+ * There is no way to name a service in either call. The scope is always the one
+ * your API key belongs to - that is the endpoint's security model, not an
+ * omission.
+ */
+export class AnalyticsResource {
+    transport;
+    constructor(transport) {
+        this.transport = transport;
+    }
+    /**
+     * Daily series for the requested metrics, up to 90 days.
+     *
+     * **Throws on failure**, unlike `emit` below. A read whose result you are
+     * about to render has to be able to say "I could not load"; silently
+     * returning an empty series would draw a chart of zeroes.
+     */
+    async series(query) {
+        const params = new URLSearchParams({
+            metrics: query.metrics.join(","),
+            from: query.from,
+            to: query.to,
+        });
+        return request(this.transport, {
+            method: "GET",
+            path: `/analytics?${params.toString()}`,
+        });
+    }
+    /**
+     * Never throws - the same judgement `LogsResource.write` makes, for the same
+     * reason: telemetry that takes down the code path it was observing is worse
+     * than a lost event. A failure is reported through `delivered`.
+     *
+     * Up to 50 events per call. Pass `sessionToken` on an event to attribute it
+     * to the signed-in user; without one it still lands, just unattributed.
+     */
+    async emit(events) {
+        const normalized = events.map((event) => ({
+            ...event,
+            occurredAt: event.occurredAt instanceof Date ? event.occurredAt.toISOString() : event.occurredAt,
+        }));
+        try {
+            const result = await request(this.transport, {
+                method: "POST",
+                path: "/events",
+                json: { events: normalized },
+            });
+            return {
+                delivered: true,
+                accepted: result?.accepted ?? events.length,
+                attributed: result?.attributed ?? 0,
+            };
+        }
+        catch {
+            return { delivered: false, accepted: 0, attributed: 0 };
+        }
+    }
+}

package/dist/esm/server/resources/identity.js

@@ -177,7 +177,7 @@ export class IdentityResource {
             throw new ConnectError({
                 status: 0,
                 code: "missing_client_id",
-                message: "identity.* needs `clientId`. Pass it to `new ConnectClient({ clientId, apiKey })` - it is shown in this service's Setup tab once SSO is enabled.",
+                message: "identity.* needs `clientId`. Pass it to `new ConnectClient({ clientId, apiKey })` - it is shown in this service's Integration tab, under Connect client.",
                 endpoint: "identity",
             });
         }