@cosmoops/connect-sdk 0.45.0 → 0.47.0

package/dist/esm/ui/page-shell.js

@@ -1,7 +1,22 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
+import * as React from "react";
 import { Suspense } from "react";
 import { ConnectPageHeader } from "./page-header.js";
 import { cn } from "../cn.js";
+/**
+ * React's `<ViewTransition>`, when the host's React has one.
+ *
+ * It ships in the React canary that Next's App Router bundles and in no stable
+ * React yet - 19.2 exports nothing by that name. So it is looked up rather
+ * than imported: a static `import { ViewTransition }` resolves to `undefined`
+ * on a Vite or Storybook host and renders as an invalid element type, which
+ * would take down every page drawn in this shell to animate it. Absent, the
+ * page renders exactly as it did before, with no motion.
+ *
+ * Read by a computed key so a bundler doing strict export checks does not
+ * warn that `react` has no such export - on those hosts it genuinely has not.
+ */
+const RouteTransition = React["ViewTransition"];
 /**
  * The frame a page opens with: its vertical rhythm, its header, and the
  * suspended regions beneath.
@@ -20,9 +35,23 @@ import { cn } from "../cn.js";
  * never be made to wait, not that every title can be static.
  *
  * `space-y-5` is the page gap, owned here so it has exactly one definition.
+ *
+ * **It is also where the route transition lives**, because it is the one
+ * thing every page opens with. A transition has to wrap the *page*: a layout
+ * persists across navigation, so its enter and exit never fire, and a
+ * `template.tsx` remounts its subtree on every navigation, discarding the
+ * form drafts and scroll positions Next's `<Activity>` keeps. Where a layout
+ * draws the shell instead - a record with tabs - entering and leaving the
+ * record animates and switching tabs does not, which is right: a tab is the
+ * same place. `default="none"` keeps it still during anything else - a
+ * filter written to the URL, a `router.refresh()` after a save. The
+ * animations are `connect-page-enter`/`connect-page-exit` in `theme.css`.
  */
-export function ConnectPageShell({ title, description, action, clamp, above, children, className, }) {
-    return (_jsxs("div", { className: cn("space-y-5", className), children: [above, title !== undefined && (_jsx(ConnectPageHeader, { title: title, description: description, action: action, clamp: clamp })), children] }));
+export function ConnectPageShell({ title, description, action, clamp, above, children, className, transition = true, }) {
+    const page = (_jsxs("div", { className: cn("space-y-5", className), children: [above, title !== undefined && (_jsx(ConnectPageHeader, { title: title, description: description, action: action, clamp: clamp })), children] }));
+    if (!transition || !RouteTransition)
+        return page;
+    return (_jsx(RouteTransition, { enter: "connect-page-enter", exit: "connect-page-exit", default: "none", children: page }));
 }
 /**
  * The page header, for a detail route that can only name itself once its data

package/dist/theme.css

@@ -97,8 +97,13 @@
    *   around a green primary button, and measured 3.33:1 against the page;
    *   indigo is a different hue from the thing it outlines and clears 5:1.
    *
-   * Green acts, indigo navigates - which is why indigo is never a fill here.
-   * A second filled hue beside the green competes for the main action.
+   * - `secondary` Buttons, as a *soft* fill - see `.button--secondary`
+   *   below. A view's main action is the solid green; the actions beside it
+   *   are an indigo tint, so they read as branded without competing.
+   *
+   * Green acts, indigo navigates and supports - which is why indigo is never
+   * a *solid* fill. A second solid hue beside the green competes for the
+   * main action.
    *
    * The hue is chosen by what is already taken: danger sits at ~13 and
    * warning at ~60-76, so green's textbook complement (magenta) would read as
@@ -110,6 +115,11 @@
   --secondary: oklch(50% 0.16 268);
   --link: var(--secondary);
   --focus: var(--secondary);
+  /* The secondary button's tint. Its text is a step darker than
+     `--secondary` so it clears 4.5:1 on the tint, not just on the page. */
+  --secondary-soft: oklch(95% 0.03 268);
+  --secondary-soft-hover: oklch(91.5% 0.05 268);
+  --secondary-soft-foreground: oklch(44% 0.16 268);
 }
 
 .dark,
@@ -137,6 +147,27 @@
   --secondary: oklch(68% 0.13 268);
   --link: var(--secondary);
   --focus: var(--secondary);
+  --secondary-soft: oklch(29% 0.06 268);
+  --secondary-soft-hover: oklch(34% 0.08 268);
+  --secondary-soft-foreground: oklch(84% 0.08 268);
+}
+
+/*
+ * The secondary button, in the secondary colour.
+ *
+ * HeroUI paints `variant="secondary"` with the neutral `--default`, which left
+ * the indigo on links and focus rings only - a page's actions were one green
+ * button and a row of grey ones, and the brand's second colour appeared on no
+ * control at all. This re-points the same four variables HeroUI's own rule
+ * sets, so hover, press, disabled and the focus ring all behave exactly as
+ * before; only the paint changes. `tertiary` stays neutral, which is what keeps
+ * an in-row control quieter than a page action.
+ */
+.button--secondary {
+  --button-bg: var(--secondary-soft);
+  --button-bg-hover: var(--secondary-soft-hover);
+  --button-bg-pressed: var(--secondary-soft-hover);
+  --button-fg: var(--secondary-soft-foreground);
 }
 
 /*
@@ -274,6 +305,51 @@ body {
   }
 }
 
+/* ---------------------------------------------------------------------------
+ * The route transition `ConnectPageShell` plays.
+ *
+ * The old page leaves fast and accelerating, so it never competes with the
+ * arrival; the new one fades in once it has gone and settles as it rises. An
+ * exit and an entrance on the same curve is the mistake these two avoid.
+ * Inert on any host whose React has no `<ViewTransition>`, which is every
+ * stable React today - see `page-shell.tsx`.
+ * ------------------------------------------------------------------------- */
+
+/* Clicks during a transition reach the live page rather than the overlay. */
+::view-transition {
+  pointer-events: none;
+}
+
+@keyframes connect-vt-fade-in {
+  from { opacity: 0; }
+}
+
+@keyframes connect-vt-fade-out {
+  to { opacity: 0; }
+}
+
+@keyframes connect-vt-rise {
+  from { transform: translateY(8px); }
+}
+
+::view-transition-old(.connect-page-exit) {
+  animation: 140ms cubic-bezier(0.64, 0, 0.78, 0) both connect-vt-fade-out;
+}
+
+::view-transition-new(.connect-page-enter) {
+  animation:
+    200ms cubic-bezier(0.22, 1, 0.36, 1) 60ms both connect-vt-fade-in,
+    260ms cubic-bezier(0.22, 1, 0.36, 1) both connect-vt-rise;
+}
+
+@media (prefers-reduced-motion: reduce) {
+  ::view-transition-old(.connect-page-exit),
+  ::view-transition-new(.connect-page-enter) {
+    animation-duration: 0s;
+    animation-delay: 0s;
+  }
+}
+
 /* ---------------------------------------------------------------------------
  * A hand-rolled button still looks pressable.
  *

package/dist/types/client/components/call-button.d.ts

@@ -25,7 +25,9 @@ import type { CallingAvailability } from "../../types.js";
  *    a number and the member must have "Make calls". What comes back lets this
  *    browser place exactly this call and no other.
  * 3. The browser places it. Connect dials the number from the workspace's own
- *    number; nothing is recorded.
+ *    number. It is recorded only when the workspace has turned recording on
+ *    (`connect.calls.getCallSettings`), and then the other party hears a
+ *    disclosure before the conversation starts.
  *
  * ## Logging a call
  *

package/dist/types/client/portal-links.d.ts

@@ -5,7 +5,7 @@
  *
  * Connect answers any of these paths for a signed-in user on the bare URL -
  * these two params only add the `"Back to <your app>"` banner
- * (`ApplicationReturnBar` on Connect's side). It validates `return_to`
+ * (the hand-off strip in `ShellAnnouncements` on Connect's side). It validates `return_to`
  * against this `client_id`'s registered redirect origins and silently drops
  * the banner if they don't match, so a wrong or stale `appUrl`/`clientId`
  * pairing degrades to what linking there did before rather than erroring.

package/dist/types/errors.d.ts

@@ -34,6 +34,13 @@ export declare class ConnectError extends Error {
      * already retries these internally (see `ConnectClientOptions.maxRetries`);
      * this is for callers deciding whether to queue their own retry after the
      * SDK has given up.
+     *
+     * **A 503 is retryable only when it carries `Retry-After`.** Connect sends
+     * that header on every 503 it means to be retried - a dependency blip, a
+     * contended transaction - and leaves it off when the dependency is
+     * *misconfigured* (a revoked provider key, say), where every retry gets the
+     * identical answer. Retrying those anyway cost a page three round trips and
+     * two sleeps per read to learn nothing.
      */
     get isRetryable(): boolean;
     /**

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

@@ -141,4 +141,4 @@ export declare class ConnectClient {
     constructor(options: ConnectClientOptions);
 }
 /** Kept in step with `package.json` by `sdk.test.ts`. */
-export declare const SDK_VERSION = "0.45.0";
+export declare const SDK_VERSION = "0.47.0";

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

@@ -26,7 +26,7 @@ export type { OtpResource } from "./resources/otp.js";
 export type { LogsResource } from "./resources/logs.js";
 export type { AnalyticsResource } from "./resources/analytics.js";
 export type { SessionsResource } from "./resources/sessions.js";
-export type { ExecuteIntegrationActionInput, InitiateIntegrationConnectionInput, IntegrationsResource, } from "./resources/integrations.js";
+export type { ExecuteIntegrationActionInput, InitiateIntegrationConnectionInput, IntegrationsResource, ProxyIntegrationRequestInput, } from "./resources/integrations.js";
 export type { PlatformResource } from "./resources/platform.js";
 export type { SchedulingResource, FindSlotsInput, ListBookingsInput, CreateBookingInput, RescheduleBookingInput, } from "./resources/scheduling.js";
 export type { ContactsResource, LookupContactInput } from "./resources/contacts.js";

package/dist/types/server/resources/drive.d.ts

@@ -1,5 +1,5 @@
 import { type TransportOptions } from "../http.js";
-import type { ThumbnailSize, UploadedFile } from "../../types.js";
+import type { DriveUsage, ThumbnailSize, UploadedFile } from "../../types.js";
 export interface UploadInput {
     workspaceId: string;
     /** Any `Blob`/`File`. In Node, `new Blob([buffer])` or `fs.openAsBlob(path)`. */
@@ -23,4 +23,11 @@ export declare class DriveResource {
         workspaceId: string;
         size?: ThumbnailSize;
     }): Promise<string>;
+    /**
+     * How much of the workspace's Drive is used, against its limit. Needs
+     * `drive:read` and an active subscription to your application.
+     */
+    getUsage(input: {
+        workspaceId: string;
+    }): Promise<DriveUsage>;
 }

package/dist/types/server/resources/integrations.d.ts

@@ -1,5 +1,5 @@
 import { type TransportOptions } from "../http.js";
-import type { DisconnectIntegrationResponse, ExecuteIntegrationActionResponse, InitiateIntegrationConnectionResponse, IntegrationsListResponse } from "../../types.js";
+import type { DisconnectIntegrationResponse, ExecuteIntegrationActionResponse, InitiateIntegrationConnectionResponse, IntegrationProxyMethod, IntegrationsListResponse, ProxyIntegrationRequestResponse } from "../../types.js";
 export interface InitiateIntegrationConnectionInput {
     toolkitSlug: string;
     returnUrl: string;
@@ -13,6 +13,13 @@ export interface InitiateIntegrationConnectionInput {
      * is present to finish the OAuth screen either.
      */
     userId: string;
+    /**
+     * Pre-fills the toolkit's own connection fields on the provider screen -
+     * `{ extension: "in" }` puts a Zoho connection on the India data centre,
+     * which otherwise defaults to `zoho.com`. Which keys a toolkit reads is
+     * Composio's catalogue; Connect passes them through.
+     */
+    connectionData?: Record<string, string>;
 }
 export interface ExecuteIntegrationActionInput {
     toolkitSlug: string;
@@ -20,6 +27,21 @@ export interface ExecuteIntegrationActionInput {
     /** Passed through to Composio verbatim - its shape is defined by the toolkit's own action schema, which Connect does not model. */
     params?: Record<string, unknown>;
 }
+export interface ProxyIntegrationRequestInput {
+    toolkitSlug: string;
+    method: IntegrationProxyMethod;
+    /**
+     * A path relative to the provider's API base - `/salesorders`, not a URL.
+     * Connect refuses anything with a scheme, a host, a `?` or a dot segment,
+     * because whoever picks the host picks where the workspace's credential
+     * goes. Parameters belong in `query`.
+     */
+    endpoint: string;
+    query?: Record<string, string>;
+    body?: unknown;
+    /** Whose connection to act through - omitted or `null` for the workspace's shared one. */
+    onBehalfOfUserId?: string | null;
+}
 /**
  * Composio-hosted third-party connections (Google Calendar, Slack,
  * Twitter/X, ...) a workspace has connected. Connect proxies every call
@@ -51,6 +73,16 @@ export declare class IntegrationsResource {
     initiateConnect(workspaceId: string, input: InitiateIntegrationConnectionInput): Promise<InitiateIntegrationConnectionResponse>;
     /** Idempotent - disconnecting a toolkit that was never connected, or is already disconnected, is a success. */
     disconnect(workspaceId: string, toolkitSlug: string): Promise<DisconnectIntegrationResponse>;
+    /**
+     * One raw request to a connected provider's own API, for an endpoint the
+     * toolkit has no action for (Zoho Books ships no "create sales order").
+     *
+     * **Resolves whenever Connect relayed the request**, whatever the provider
+     * answered: read `status` and `data` for that. A provider-side 4xx is a
+     * business answer ("that GSTIN is invalid") rather than a transport
+     * failure, so it is not thrown as one.
+     */
+    request(workspaceId: string, input: ProxyIntegrationRequestInput): Promise<ProxyIntegrationRequestResponse>;
     /** Calls a Composio action against this workspace's connected account for the named toolkit. */
     execute(workspaceId: string, input: ExecuteIntegrationActionInput): Promise<ExecuteIntegrationActionResponse>;
 }

package/dist/types/server/resources/workspaces.d.ts

@@ -104,9 +104,18 @@ export declare class WorkspacesResource {
      * Connect roles - so you never reimplement Connect's role resolution, and
      * you are told nothing about the customer's Connect account beyond what your
      * application needs.
+     *
+     * **Seat holders only, by default.** A workspace member with no seat on your
+     * application cannot sign in to it, so they are not part of your team and
+     * do not belong in an owner picker or an assignee list. Pass
+     * `includeUnassigned: true` from the screen where an admin *gives* a seat -
+     * it needs the people who do not have one yet. That form needs the signed-in
+     * member to be able to change access (a 403 otherwise), and every row
+     * carries `assigned` so the screen can tell the two apart.
      */
     members(options: {
         asUser: string;
+        includeUnassigned?: boolean;
     }): Promise<ConnectWorkspaceMember[]>;
     /**
      * Seats, what the caller may do with them, and the invitations already

package/dist/types/types.d.ts

@@ -588,6 +588,15 @@ export interface UploadedFile {
     size: number;
     url: string;
 }
+/**
+ * How full a workspace's Drive is. The limit is the one an upload is refused
+ * against, so a meter built on this agrees with `quota_exceeded`.
+ */
+export interface DriveUsage {
+    usedBytes: number;
+    /** `null` = unlimited. */
+    limitBytes: number | null;
+}
 export type ThumbnailSize = "small" | "medium" | "large";
 export type LogLevel = "debug" | "info" | "warn" | "error";
 export interface WriteLogInput {
@@ -1043,6 +1052,12 @@ export interface ExecuteIntegrationActionResponse {
     data: unknown;
     successful: boolean;
 }
+export type IntegrationProxyMethod = "GET" | "POST" | "PUT" | "PATCH" | "DELETE";
+/** See `IntegrationsResource.request` - `status` is the provider's, not Connect's. */
+export interface ProxyIntegrationRequestResponse {
+    status: number;
+    data: unknown;
+}
 /**
  * The metrics Connect can report for your application.
  *
@@ -1903,6 +1918,12 @@ export interface ConnectWorkspaceMember {
      */
     memberId: string;
     userId: string;
+    /**
+     * Whether this member holds a seat on your application. Only assigned
+     * members can sign in to it; unassigned rows appear only when you asked
+     * for them with `members({ includeUnassigned: true })`, to assign from.
+     */
+    assigned: boolean;
     email: string;
     displayName: string | null;
     photoUrl: string | null;

package/dist/types/ui/page-shell.d.ts

@@ -1,3 +1,4 @@
+import * as React from "react";
 import { type ReactNode } from "react";
 import { ConnectPageHeader } from "./page-header.js";
 export interface ConnectPageShellProps {
@@ -13,6 +14,12 @@ export interface ConnectPageShellProps {
      * See `cn`.
      */
     className?: string;
+    /**
+     * The route transition - the outgoing page fades out, the arriving one fades
+     * in and rises. On by default; pass `false` where a host already animates
+     * its routes, or the two play over each other. See {@link RouteTransition}.
+     */
+    transition?: boolean;
     children?: ReactNode;
 }
 /**
@@ -33,13 +40,24 @@ export interface ConnectPageShellProps {
  * never be made to wait, not that every title can be static.
  *
  * `space-y-5` is the page gap, owned here so it has exactly one definition.
+ *
+ * **It is also where the route transition lives**, because it is the one
+ * thing every page opens with. A transition has to wrap the *page*: a layout
+ * persists across navigation, so its enter and exit never fire, and a
+ * `template.tsx` remounts its subtree on every navigation, discarding the
+ * form drafts and scroll positions Next's `<Activity>` keeps. Where a layout
+ * draws the shell instead - a record with tabs - entering and leaving the
+ * record animates and switching tabs does not, which is right: a tab is the
+ * same place. `default="none"` keeps it still during anything else - a
+ * filter written to the URL, a `router.refresh()` after a save. The
+ * animations are `connect-page-enter`/`connect-page-exit` in `theme.css`.
  */
-export declare function ConnectPageShell({ title, description, action, clamp, above, children, className, }: Readonly<ConnectPageShellProps>): import("react").JSX.Element;
+export declare function ConnectPageShell({ title, description, action, clamp, above, children, className, transition, }: Readonly<ConnectPageShellProps>): React.JSX.Element;
 export declare namespace ConnectPageShell {
     var Header: typeof ConnectPageHeader;
     var Async: ({ fallback, children, }: Readonly<{
         /** Omit where the region has nothing to draw while it waits. */
         fallback?: ReactNode;
         children: ReactNode;
-    }>) => import("react").JSX.Element;
+    }>) => React.JSX.Element;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmoops/connect-sdk",
-  "version": "0.45.0",
+  "version": "0.47.0",
   "description": "Official server-side SDK for the CosmoOps Connect platform API - Login with Connect, entitlements, billing and metering.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "commonjs",