@vercel/connect 0.0.4-alpha.9 → 0.0.5-alpha.1

package/README.md

@@ -55,7 +55,7 @@ function getTokenResponse(
 ): Promise<ConnectTokenResponse>;
 ```
 
-Returns the full token response including `expiresAt`, `installationId`, `tenantId`, and `externalSubject`. Use this when you need the expiration or any of the metadata fields.
+Returns the full token response including `expiresAt`, connector identity (`connector`), `installationId`, `tenantId`, and `externalSubject`. Use this when you need the expiration or any of the metadata fields.
 
 Both functions share an in-process LRU cache (max 100 entries) keyed by `connector` plus the full `params` payload. Cached entries are reused until they fall inside the `validityBufferMs` window before expiration, after which they're refetched.
 
@@ -103,6 +103,14 @@ interface ConnectTokenResponse {
   token: string;
   /** Expiration timestamp in ms since epoch. */
   expiresAt: number;
+  connector: {
+    /** Opaque Vercel Connect connector id. */
+    id: string;
+    /** Human-readable Vercel Connect connector UID. */
+    uid: string;
+    /** Vercel Connect connector type identifier. */
+    type: string;
+  };
   name?: string;
   installationId?: string;
   tenantId?: string;
@@ -167,7 +175,7 @@ try {
 
 ## `@vercel/connect/ash`
 
-Adapter helpers for the [Ash](https://github.com/vercel/ash) connection runtime. Importing this subpath requires `experimental-ash >= 0.3.0-alpha.19` to be installed in the consumer project.
+Adapter helpers for the [Ash](https://github.com/vercel/ash) connection runtime. Importing this subpath requires `experimental-ash >= 0.8.2` to be installed in the consumer project.
 
 ### `connect(input)`
 
@@ -176,13 +184,17 @@ Builds an Ash `AuthorizationDefinition` backed by Vercel Connect, collapsing the
 ```ts
 function connect(
   connector: string,
-): InteractiveAuthorizationDefinition<ConnectAuthorizationState>;
+): AshConnectAuthorizationDefinition<
+  InteractiveAuthorizationDefinition<ConnectAuthorizationState>
+>;
 function connect(
   options: AshAuthorizationOptions & { principalType?: "user" },
-): InteractiveAuthorizationDefinition<ConnectAuthorizationState>;
+): AshConnectAuthorizationDefinition<
+  InteractiveAuthorizationDefinition<ConnectAuthorizationState>
+>;
 function connect(
   options: AshAuthorizationOptions & { principalType: "app" },
-): NonInteractiveAuthorizationDefinition;
+): AshConnectAuthorizationDefinition<NonInteractiveAuthorizationDefinition>;
 ```
 
 The shorthand form `connect("linear")` is equivalent to `connect({ connector: "linear" })` — `principalType` defaults to `"user"`, so the helper returns an interactive definition unless you opt into `"app"` explicitly.
@@ -219,6 +231,18 @@ export default defineMcpClientConnection({
 ```ts
 type AshAuthorizationInput = string | AshAuthorizationOptions;
 
+interface VercelConnectMetadata {
+  readonly connector: string;
+}
+
+type AshConnectAuthorizationDefinition<
+  TAuthorization extends
+    | InteractiveAuthorizationDefinition<ConnectAuthorizationState>
+    | NonInteractiveAuthorizationDefinition,
+> = TAuthorization & {
+  readonly vercelConnect: VercelConnectMetadata;
+};
+
 type ConnectAuthorizationPhase =
   | "getToken"
   | "startAuthorization"

package/dist/token.d.ts

@@ -24,6 +24,14 @@ export interface ConnectTokenResponse {
     token: string;
     /** Token expiration timestamp in milliseconds since epoch. */
     expiresAt: number;
+    connector: {
+        /** Opaque Vercel Connect connector id. */
+        id: string;
+        /** Human-readable Vercel Connect connector UID. */
+        uid: string;
+        /** Vercel Connect connector type identifier. */
+        type: string;
+    };
     name?: string;
     installationId?: string;
     tenantId?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/connect",
-  "version": "0.0.4-alpha.9",
+  "version": "0.0.5-alpha.1",
   "license": "Apache-2.0",
   "type": "module",
   "exports": {