@theholocron/holocron-plugin-vercel 5.0.0-alpha.26 → 5.0.0-alpha.28

package/README.md

@@ -64,9 +64,25 @@ Capability covers:
   an app) — `defaultFramework` only applies to `ensureProject()`'s
   Git-linked path.
 - `getDeployment()` — fetch a deployment by id
+- `ensureCustomDomain()` — idempotent add (list → check → add). Adding
+  a domain new to the Vercel account returns `verified: false` with a
+  DNS verification challenge (usually a CNAME to a per-project target
+  Vercel generates — never a fixed well-known host). The returned DNS
+  record is handed to the configured `dns` provider by `holocron setup`.
+
+Declare the production domain in the Vercel provider options. On `holocron setup`,
+the domain is attached to the project and any Vercel verification CNAME is
+upserted through the configured DNS provider:
+
+```ts
+providers: {
+	deployment: ["vercel", { teamId: "team_…", domain: "sentinel.example.com" }],
+	dns: "cloudflare",
+}
+```
 
 Out of scope for alpha.0 (file a follow-up if needed):
 
-- Domain management (`addDomain` / `removeDomain`)
+- Domain removal (`removeDomain`)
 - Deletion (`deleteProject`)
 - Marketplace integrations (e.g. `vercel install neon` for vault-managed databases)

package/dist/index.d.mts

@@ -1,4 +1,4 @@
-import { AuthError, DeployFunctionConfig, DeployFunctionResult, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, ResolveTokenInput } from "@theholocron/cli";
+import { AuthError, DeployFunctionConfig, DeployFunctionResult, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, DnsRecordRequest, ResolveTokenInput } from "@theholocron/cli";
 import { VercelClient, VercelClient as VercelClient$1, VercelClientOptions, createVercelClient } from "@theholocron/vercel-client";
 //#region src/auth.d.ts
 declare const resolveToken: (input?: ResolveTokenInput) => string;
@@ -7,11 +7,14 @@ declare const resolveToken: (input?: ResolveTokenInput) => string;
 interface DeploymentOptions {
   /** Optional framework hint passed to project creates. Defaults to "nextjs". */
   defaultFramework?: string;
+  /** Custom domain that `holocron setup` should attach to this project. */
+  domain?: string;
 }
 declare class VercelDeployment implements Deployment {
   private readonly client;
   readonly key: "deployment";
   readonly providerName = "vercel";
+  readonly domain?: string;
   private readonly defaultFramework;
   constructor(client: () => VercelClient$1, opts?: DeploymentOptions);
   listProjects(): Promise<DeploymentProject[]>;
@@ -31,6 +34,19 @@ declare class VercelDeployment implements Deployment {
   }): Promise<DeploymentRecord>;
   getDeployment(deploymentId: string): Promise<DeploymentRecord>;
   deployFunction(projectId: string, config: DeployFunctionConfig): Promise<DeployFunctionResult>;
+  /**
+   * Idempotent — no-op when `hostname` is already on the project,
+   * matching `Deployment.ensureCustomDomain`'s contract (never break
+   * on re-runs, per CLAUDE.md's probe-then-act standard). Adding it
+   * the first time returns `verified: false` for a domain new to this
+   * Vercel account, plus a `verification` challenge — usually CNAME, a
+   * unique per-project target Vercel generates (never a fixed
+   * well-known host, confirmed via Vercel's own docs). Returned as a
+   * `DnsRecordRequest` — the caller (e.g. `holocron setup`'s
+   * custom-domain step) hands it straight to `dns.upsertRecord()`,
+   * same as `Wiki.dnsRecord()` already does for the wiki's own domain.
+   */
+  ensureCustomDomain(projectId: string, hostname: string): Promise<DnsRecordRequest | null>;
   private getProjectByName;
 }
 //#endregion
@@ -61,6 +77,8 @@ interface VercelPluginOptions extends ResolveTokenInput {
   teamId?: string;
   /** Default framework slug for new project creates. Defaults to "nextjs". */
   defaultFramework?: string;
+  /** Custom domain that `holocron setup` should attach to the Vercel project. */
+  domain?: string;
   /** Override base URL for tests. */
   baseUrl?: string;
   /** Override `fetch` for tests. */

package/dist/index.mjs

@@ -13,10 +13,12 @@ var VercelDeployment = class {
 	client;
 	key = "deployment";
 	providerName = "vercel";
+	domain;
 	defaultFramework;
 	constructor(client, opts = {}) {
 		this.client = client;
 		this.defaultFramework = opts.defaultFramework ?? "nextjs";
+		this.domain = opts.domain;
 	}
 	async listProjects() {
 		const { projects } = await this.client().projects.list();
@@ -75,6 +77,34 @@ var VercelDeployment = class {
 			url: raw.url
 		};
 	}
+	/**
+	* Idempotent — no-op when `hostname` is already on the project,
+	* matching `Deployment.ensureCustomDomain`'s contract (never break
+	* on re-runs, per CLAUDE.md's probe-then-act standard). Adding it
+	* the first time returns `verified: false` for a domain new to this
+	* Vercel account, plus a `verification` challenge — usually CNAME, a
+	* unique per-project target Vercel generates (never a fixed
+	* well-known host, confirmed via Vercel's own docs). Returned as a
+	* `DnsRecordRequest` — the caller (e.g. `holocron setup`'s
+	* custom-domain step) hands it straight to `dns.upsertRecord()`,
+	* same as `Wiki.dnsRecord()` already does for the wiki's own domain.
+	*/
+	async ensureCustomDomain(projectId, hostname) {
+		const { domains: existing } = await this.client().domains.list(projectId);
+		if (existing.some((d) => d.name === hostname)) return null;
+		const result = await this.client().domains.add(projectId, hostname);
+		if (result.verified) return null;
+		const challenge = result.verification?.find((v) => v.type === "CNAME");
+		if (!challenge) return null;
+		return {
+			zone: result.apexName,
+			record: {
+				type: "CNAME",
+				name: hostname,
+				content: challenge.value
+			}
+		};
+	}
 	async getProjectByName(name) {
 		try {
 			return mapProject(await this.client().projects.get(name));
@@ -157,6 +187,7 @@ function createContext(options = {}) {
 function deployment(ctx) {
 	const opts = {};
 	if (ctx.options.defaultFramework !== void 0) opts.defaultFramework = ctx.options.defaultFramework;
+	if (ctx.options.domain !== void 0) opts.domain = ctx.options.domain;
 	return new VercelDeployment(ctx.client, opts);
 }
 function createPlugin(options = {}) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-vercel",
-  "version": "5.0.0-alpha.26",
+  "version": "5.0.0-alpha.28",
   "description": "Holocron plugin for Vercel. Implements the deployment capability against the Vercel REST API.",
   "keywords": [
     "deployment",
@@ -31,10 +31,10 @@
   ],
   "devDependencies": {
     "@theholocron/eslint-config": "^8.0.0",
-    "@theholocron/http-client": "^1.22.0",
+    "@theholocron/http-client": "^1.23.0",
     "@theholocron/tsconfig": "^8.0.0",
     "@theholocron/tsdown-config": "^8.0.0",
-    "@theholocron/vercel-client": "^1.22.0",
+    "@theholocron/vercel-client": "^1.23.0",
     "@theholocron/vitest-config": "^8.0.0",
     "@types/node": "^26",
     "@vitest/coverage-v8": "^4.1.11",
@@ -46,11 +46,11 @@
     "tsx": "4.23.12",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11",
-    "@theholocron/cli": "5.0.0-alpha.26"
+    "@theholocron/cli": "5.0.0-alpha.28"
   },
   "peerDependencies": {
-    "@theholocron/vercel-client": "^1.22.0",
-    "@theholocron/cli": "5.0.0-alpha.26"
+    "@theholocron/vercel-client": "^1.23.0",
+    "@theholocron/cli": "5.0.0-alpha.28"
   },
   "peerDependenciesMeta": {
     "@theholocron/vercel-client": {}