create-kontrolia-auth 2.2.0 → 2.2.1

package/README.md

@@ -22,10 +22,11 @@ Eso hace, en orden:
 4. **Primera aplicación** (opcional): registra tu app y su catálogo de permisos.
 5. **Despliegue**: genera los `.env.local` de `auth-server` y `admin-panel`. Si
    eliges Vercel y el repo ya está en GitHub, puede **crear los dos proyectos
-   por ti** vía la API de Vercel (carpeta y variables de entorno correctas de
-   una vez, sin tocar el dashboard ni la CLI de Vercel) — solo pide un API
-   token de vercel.com/account/tokens. Para Docker, Railway, Render o
-   Coolify te da los pasos exactos.
+   y desplegarlos por ti** vía la API de Vercel (carpeta y variables de
+   entorno correctas, y el primer build disparado automáticamente — sin
+   tocar el dashboard ni la CLI de Vercel) — solo pide un API token de
+   vercel.com/account/tokens (el instalador explica cómo generarlo). Para
+   Docker, Railway, Render o Coolify te da los pasos exactos.
 
 Si ya estás **dentro del repo** (desarrollo), el instalador lo detecta y se
 salta la descarga:

package/dist/steps/deployment.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"deployment.d.ts","sourceRoot":"","sources":["../../src/steps/deployment.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AA6GpD;;;;GAIG;AACH,wBAAsB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,EAAE,EAAE,EAAE,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,CAwI3F"}
+{"version":3,"file":"deployment.d.ts","sourceRoot":"","sources":["../../src/steps/deployment.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AA8JpD;;;;GAIG;AACH,wBAAsB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,EAAE,EAAE,EAAE,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,CAwI3F"}

package/dist/steps/deployment.js

@@ -1,7 +1,7 @@
 import * as p from "@clack/prompts";
 import { updateEnvValue, writeEnvFile } from "../utils/files.js";
 import { registerOAuthClient } from "../utils/oauth-client.js";
-import { createVercelProject, detectGitHubRepo } from "../utils/vercel-api.js";
+import { createVercelProject, detectCurrentBranch, detectGitHubRepo, triggerVercelDeployment } from "../utils/vercel-api.js";
 const NEXT_STEPS = {
     docker: "Ya está: los servicios auth-server y admin-panel viven en el mismo docker/docker-compose.yml. Corre `docker compose -f docker/docker-compose.yml up -d` para tenerlos arriba.",
     vercel: "Lo más confiable con un monorepo pnpm es conectar el repo desde el dashboard (no desplegar carpetas sueltas por CLI):\n" +
@@ -28,12 +28,48 @@ const NEXT_STEPS = {
     manual: "Corre `pnpm build && pnpm start` en apps/auth-server y apps/admin-panel en el servidor/K8s de tu elección, usando los .env.local generados.",
 };
 /**
- * Offers to create both Vercel projects via the REST API instead of walking
- * the user through the dashboard/CLI by hand — the same three fields that
- * are easy to get wrong doing this manually (gitRepository, rootDirectory,
- * environmentVariables) are just fields in one request body here. Returns
- * true only if both projects were created, so the caller knows whether to
- * still show the manual fallback instructions.
+ * Creates one Vercel project and immediately triggers its first deployment
+ * — creating the project alone only connects the GitHub repo, it doesn't
+ * build or deploy anything by itself, so skipping this step would leave the
+ * user with a project that just sits there until something else (a push, or
+ * clicking "Deploy" by hand) triggers a build. Reports both outcomes
+ * separately since either can fail independently of the other.
+ */
+async function createAndDeployVercelProject(options) {
+    const createSpinner = p.spinner();
+    createSpinner.start(`Creando proyecto de Vercel para ${options.appLabel}`);
+    const created = await createVercelProject({
+        token: options.token,
+        repo: options.repo,
+        name: options.projectName,
+        rootDirectory: options.rootDirectory,
+        env: options.env,
+    });
+    createSpinner.stop(created.ok ? `Proyecto ${options.appLabel} creado` : `Falló creando ${options.appLabel}: ${created.error}`);
+    if (!created.ok)
+        return false;
+    const deploySpinner = p.spinner();
+    deploySpinner.start(`Desplegando ${options.appLabel} (primer build)`);
+    const deployed = await triggerVercelDeployment({
+        token: options.token,
+        repo: options.repo,
+        branch: options.branch,
+        projectName: options.projectName,
+    });
+    deploySpinner.stop(deployed.ok
+        ? `${options.appLabel} desplegándose — sigue el progreso en vercel.com/dashboard`
+        : `Proyecto creado, pero no se pudo disparar el despliegue: ${deployed.error} — dale "Deploy" a mano en el dashboard.`);
+    return true;
+}
+/**
+ * Offers to create both Vercel projects (and deploy them) via the REST API
+ * instead of walking the user through the dashboard/CLI by hand — the same
+ * fields that are easy to get wrong doing this manually (gitRepository,
+ * rootDirectory, environmentVariables) are just fields in two request
+ * bodies here. Returns true if both projects were at least created, so the
+ * caller knows whether to still show the manual fallback instructions (a
+ * project that was created but failed to deploy still doesn't need those —
+ * the user just clicks "Deploy" once in the dashboard).
  */
 async function tryAutoCreateVercelProjects(repoRoot, authServerEnv, adminPanelEnv) {
     const repo = await detectGitHubRepo(repoRoot);
@@ -44,41 +80,43 @@ async function tryAutoCreateVercelProjects(repoRoot, authServerEnv, adminPanelEn
         return false;
     }
     const auto = await p.confirm({
-        message: `¿Quieres que cree los dos proyectos de Vercel automáticamente (conectados a ${repo}, con sus variables ya puestas)? Solo necesito un API token de Vercel.`,
+        message: `¿Quieres que cree y despliegue los dos proyectos de Vercel automáticamente (conectados a ${repo}, con sus variables ya puestas)? Solo necesito un API token de Vercel.`,
         initialValue: true,
     });
     if (p.isCancel(auto) || !auto)
         return false;
+    p.note("1. Entra a vercel.com/account/tokens (inicia sesión con tu cuenta de Vercel si te lo pide)\n" +
+        '2. Dale click a "Create Token"\n' +
+        '3. Ponle un nombre (por ejemplo "kontrolia-auth"), deja lo demás por defecto y confirma\n' +
+        "4. Copia el token que te muestra (solo se ve una vez) y pégalo aquí abajo", "Cómo conseguir el API token de Vercel");
     const token = await p.password({
-        message: "API token de Vercel (vercel.com/account/tokens — no se guarda, solo se usa ahora)",
+        message: "API token de Vercel (no se guarda, solo se usa ahora)",
         validate: (value) => (value.trim() ? undefined : "Requerido"),
     });
     if (p.isCancel(token))
         return false;
+    const branch = await detectCurrentBranch(repoRoot);
     const namePrefix = repo.split("/")[1] ?? "kontrolia-auth";
-    const authSpinner = p.spinner();
-    authSpinner.start("Creando proyecto de Vercel para auth-server");
-    const authResult = await createVercelProject({
+    const authOk = await createAndDeployVercelProject({
         token,
         repo,
-        name: `${namePrefix}-auth-server`,
+        branch,
+        appLabel: "auth-server",
+        projectName: `${namePrefix}-auth-server`,
         rootDirectory: "apps/auth-server",
         env: authServerEnv,
     });
-    authSpinner.stop(authResult.ok ? "Proyecto auth-server creado" : `Falló auth-server: ${authResult.error}`);
-    const adminSpinner = p.spinner();
-    adminSpinner.start("Creando proyecto de Vercel para admin-panel");
-    const adminResult = await createVercelProject({
+    const adminOk = await createAndDeployVercelProject({
         token,
         repo,
-        name: `${namePrefix}-admin-panel`,
+        branch,
+        appLabel: "admin-panel",
+        projectName: `${namePrefix}-admin-panel`,
         rootDirectory: "apps/admin-panel",
         env: adminPanelEnv,
     });
-    adminSpinner.stop(adminResult.ok ? "Proyecto admin-panel creado" : `Falló admin-panel: ${adminResult.error}`);
-    if (authResult.ok && adminResult.ok) {
-        p.note("Los dos proyectos ya están conectados a tu repo, con la carpeta y las variables correctas. Entra a " +
-            "vercel.com/dashboard y dale \"Deploy\" a cada uno (o empuja un commit a tu rama principal) para el primer despliegue.", "Listo");
+    if (authOk && adminOk) {
+        p.note("Revisa el progreso del build en vercel.com/dashboard — cada uno toma un par de minutos.", "Listo");
         return true;
     }
     p.note("Algo falló creando los proyectos — usa los pasos manuales de abajo para lo que no se haya creado.", "Revisa el error de arriba");

package/dist/utils/vercel-api.d.ts

@@ -7,6 +7,8 @@ import type { EnvValues } from "./files.js";
  * but this product's docs and CLI only ever assume GitHub.
  */
 export declare function detectGitHubRepo(repoRoot: string): Promise<string | null>;
+/** The branch actually checked out — what should get deployed, not an assumed "main". */
+export declare function detectCurrentBranch(repoRoot: string): Promise<string>;
 export interface CreateVercelProjectOptions {
     token: string;
     /** "owner/repo" on GitHub. */
@@ -32,4 +34,23 @@ export interface CreateVercelProjectResult {
  * https://vercel.com/docs/rest-api/reference/endpoints/projects/create-a-new-project
  */
 export declare function createVercelProject(options: CreateVercelProjectOptions): Promise<CreateVercelProjectResult>;
+export interface TriggerDeploymentOptions {
+    token: string;
+    /** "owner/repo" on GitHub. */
+    repo: string;
+    branch: string;
+    /** Must match the `name` used in createVercelProject — that's how this targets the right project. */
+    projectName: string;
+}
+/**
+ * Creating a project via the API (createVercelProject above) connects the
+ * GitHub repo but does NOT build or deploy anything by itself — that's a
+ * separate resource. Without this, a freshly created project just sits
+ * there until something else (a push, or clicking "Deploy" in the
+ * dashboard) triggers its first build, which defeats the point of
+ * automating this in the first place.
+ *
+ * https://vercel.com/docs/rest-api/reference/endpoints/deployments/create-a-new-deployment
+ */
+export declare function triggerVercelDeployment(options: TriggerDeploymentOptions): Promise<CreateVercelProjectResult>;
 //# sourceMappingURL=vercel-api.d.ts.map

package/dist/utils/vercel-api.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"vercel-api.d.ts","sourceRoot":"","sources":["../../src/utils/vercel-api.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,YAAY,CAAC;AAE5C;;;;;;GAMG;AACH,wBAAsB,gBAAgB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CAQ/E;AAED,MAAM,WAAW,0BAA0B;IACzC,KAAK,EAAE,MAAM,CAAC;IACd,8BAA8B;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,aAAa,EAAE,MAAM,CAAC;IACtB,GAAG,EAAE,SAAS,CAAC;CAChB;AAED,MAAM,WAAW,yBAAyB;IACxC,EAAE,EAAE,OAAO,CAAC;IACZ,qCAAqC;IACrC,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED;;;;;;;;;;GAUG;AACH,wBAAsB,mBAAmB,CAAC,OAAO,EAAE,0BAA0B,GAAG,OAAO,CAAC,yBAAyB,CAAC,CAgCjH"}
+{"version":3,"file":"vercel-api.d.ts","sourceRoot":"","sources":["../../src/utils/vercel-api.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,YAAY,CAAC;AAE5C;;;;;;GAMG;AACH,wBAAsB,gBAAgB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CAQ/E;AAED,yFAAyF;AACzF,wBAAsB,mBAAmB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAO3E;AAED,MAAM,WAAW,0BAA0B;IACzC,KAAK,EAAE,MAAM,CAAC;IACd,8BAA8B;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,aAAa,EAAE,MAAM,CAAC;IACtB,GAAG,EAAE,SAAS,CAAC;CAChB;AAED,MAAM,WAAW,yBAAyB;IACxC,EAAE,EAAE,OAAO,CAAC;IACZ,qCAAqC;IACrC,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED;;;;;;;;;;GAUG;AACH,wBAAsB,mBAAmB,CAAC,OAAO,EAAE,0BAA0B,GAAG,OAAO,CAAC,yBAAyB,CAAC,CAgCjH;AAED,MAAM,WAAW,wBAAwB;IACvC,KAAK,EAAE,MAAM,CAAC;IACd,8BAA8B;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,MAAM,EAAE,MAAM,CAAC;IACf,qGAAqG;IACrG,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;;;;;;;;GASG;AACH,wBAAsB,uBAAuB,CAAC,OAAO,EAAE,wBAAwB,GAAG,OAAO,CAAC,yBAAyB,CAAC,CAyBnH"}

package/dist/utils/vercel-api.js

@@ -16,6 +16,16 @@ export async function detectGitHubRepo(repoRoot) {
         return null;
     }
 }
+/** The branch actually checked out — what should get deployed, not an assumed "main". */
+export async function detectCurrentBranch(repoRoot) {
+    try {
+        const branch = (await run("git", ["branch", "--show-current"], { cwd: repoRoot })).trim();
+        return branch || "main";
+    }
+    catch {
+        return "main";
+    }
+}
 /**
  * Creates a Vercel project via the REST API — connected to the GitHub repo,
  * scoped to one app's folder in this monorepo, with its environment
@@ -59,3 +69,38 @@ export async function createVercelProject(options) {
     const body = (await response.json().catch(() => null));
     return { ok: false, error: body?.error?.message ?? `HTTP ${response.status}` };
 }
+/**
+ * Creating a project via the API (createVercelProject above) connects the
+ * GitHub repo but does NOT build or deploy anything by itself — that's a
+ * separate resource. Without this, a freshly created project just sits
+ * there until something else (a push, or clicking "Deploy" in the
+ * dashboard) triggers its first build, which defeats the point of
+ * automating this in the first place.
+ *
+ * https://vercel.com/docs/rest-api/reference/endpoints/deployments/create-a-new-deployment
+ */
+export async function triggerVercelDeployment(options) {
+    const [org, repo] = options.repo.split("/");
+    let response;
+    try {
+        response = await fetch("https://api.vercel.com/v13/deployments", {
+            method: "POST",
+            headers: {
+                Authorization: `Bearer ${options.token}`,
+                "Content-Type": "application/json",
+            },
+            body: JSON.stringify({
+                name: options.projectName,
+                target: "production",
+                gitSource: { type: "github", ref: options.branch, org, repo },
+            }),
+        });
+    }
+    catch (error) {
+        return { ok: false, error: error.message };
+    }
+    if (response.ok)
+        return { ok: true };
+    const body = (await response.json().catch(() => null));
+    return { ok: false, error: body?.error?.message ?? `HTTP ${response.status}` };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-kontrolia-auth",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "license": "MIT",
   "description": "Turnkey installer for KontrolIA Auth. `npx create-kontrolia-auth mi-app` checks requirements, downloads the repo, installs deps, and runs a wizard: (1) connect to an existing Supabase project or create a new self-hosted one via Docker; (2) where to deploy auth-server/admin-panel (Docker, Vercel, Railway, Render, Coolify). Also exposes `update`, `migrate` and `doctor` subcommands.",
   "keywords": [