@vercel/connect 0.3.1 → 0.3.3

package/dist/authorization.d.ts

@@ -12,5 +12,28 @@ export interface ConnectAuthorizationResponse {
     url: string;
     deviceCode?: string;
     expiresAt?: number;
+    /**
+     * Connector (client) being authorized, matching the `connector`
+     * object on the Vercel Connect token response. Present once the
+     * Vercel API supports returning it.
+     */
+    connector?: {
+        /** Client id. */
+        id: string;
+        /** Client uid. */
+        uid: string;
+        /** Client type, eg. `oauth`, `salesforce`. */
+        type: string;
+        /** Resolved service id when known, eg. `salesforce`. */
+        service?: string;
+        /**
+         * Curated display name of the resolved service, eg. `Salesforce`,
+         * present when the service is known to Vercel Connect. Suited for
+         * end-user surfaces like "Sign in with {serviceName}".
+         */
+        serviceName?: string;
+        /** The connector's own (operator-given) name. */
+        name: string;
+    };
 }
 export declare function startAuthorization(connector: string, params: ConnectTokenParams, options?: ConnectAuthorizationOptions): Promise<ConnectAuthorizationResponse>;

package/dist/eve/connection-authorization.d.ts

@@ -157,6 +157,14 @@ export interface EveAuthorizationOptions {
      * from the connection's filename.
      */
     readonly instructions?: string;
+    /**
+     * Manual override for the human-readable provider name channels
+     * render on the authorization affordance (eg. a
+     * `Sign in with Salesforce` button). When omitted, the connector's
+     * service display name reported by Vercel Connect is used, falling
+     * back to the connector's own name for unknown services.
+     */
+    readonly displayName?: string;
     /**
      * Escape hatch for turning an unexpected Vercel Connect / network
      * error into an Eve-recognizable error. Called once per failure

package/dist/eve/connection-authorization.js

@@ -121,6 +121,14 @@ function buildInteractiveDefinition(options) {
                     ...(completionWebhook ? { webhook: completionWebhook } : null),
                     deviceCode: true,
                 });
+                // Sign-in buttons name the destination service ("Sign in with
+                // Salesforce"), matching the OAuth idiom — the consent screen
+                // names the specific requesting app. The connector's own name is
+                // the fallback for custom connectors on unknown services, and an
+                // author-provided override wins over both.
+                const displayName = options.displayName ??
+                    response.connector?.serviceName ??
+                    response.connector?.name;
                 return {
                     challenge: {
                         url: response.url,
@@ -131,6 +139,7 @@ function buildInteractiveDefinition(options) {
                         ...(options.instructions
                             ? { instructions: options.instructions }
                             : null),
+                        ...(displayName ? { displayName } : null),
                     },
                 };
             }

package/dist/token.d.ts

@@ -38,6 +38,11 @@ export interface ConnectTokenParams {
 }
 export interface ConnectTokenResponse {
     token: string;
+    /**
+     * Per-issuance identifier for the token (`stk_…`), stable for its lifetime;
+     * use it to correlate the token with its usage in Vercel observability data.
+     */
+    tokenId?: string;
     /** Token expiration timestamp in milliseconds since epoch. */
     expiresAt: number;
     connector: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/connect",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "license": "Apache-2.0",
   "type": "module",
   "repository": {