create-kontrolia-auth 2.4.2 → 2.4.4

package/dist/index.js

@@ -6,10 +6,23 @@ import { askDatabaseStep } from "./steps/database.js";
 import { askDeploymentStep } from "./steps/deployment.js";
 import { bringUpAndMigrate } from "./utils/docker.js";
 import { readEnvFile } from "./utils/files.js";
+import { openBrowser } from "./utils/open-browser.js";
 import { runPreflight } from "./utils/preflight.js";
 import { textOrExit } from "./utils/prompts.js";
 import { ensureRepo, isInsideRepo } from "./utils/scaffold.js";
 import { pullLatest } from "./utils/update.js";
+/** Best-effort host extraction from a Postgres connection string, for the confirmation prompt below. Never throws — an unparseable string just skips the localhost check and confirms anyway. */
+function connectionHost(connectionString) {
+    try {
+        return new URL(connectionString.replace(/^postgres(ql)?:/, "postgresql:")).hostname || null;
+    }
+    catch {
+        return null;
+    }
+}
+function isLocalHost(host) {
+    return host === null || host === "localhost" || host === "127.0.0.1" || host === "::1" || host === "db";
+}
 /** Applies the schema against an already-reachable database, with a spinner. */
 async function migrateWithSpinner(connectionString) {
     const s = p.spinner();
@@ -37,6 +50,17 @@ async function runMigrateCommand() {
         p.cancel("Cancelado.");
         process.exit(0);
     }
+    const host = connectionHost(url);
+    if (!isLocalHost(host)) {
+        const proceed = await p.confirm({
+            message: `Esta connection string apunta a "${host}", que no parece ser una base de datos local. ¿Aplicar las migraciones de kontrolia_auth ahí?`,
+            initialValue: false,
+        });
+        if (p.isCancel(proceed) || !proceed) {
+            p.cancel("Cancelado.");
+            process.exit(0);
+        }
+    }
     const ok = await migrateWithSpinner(url);
     if (!ok)
         process.exitCode = 1;
@@ -128,6 +152,17 @@ async function runUpdateCommand() {
         p.outro("Código actualizado. Corre `npx create-kontrolia-auth migrate` cuando quieras aplicar la base de datos.");
         return;
     }
+    const updateHost = connectionHost(url);
+    if (!isLocalHost(updateHost)) {
+        const proceed = await p.confirm({
+            message: `Esta connection string apunta a "${updateHost}", que no parece ser una base de datos local. ¿Aplicar las migraciones nuevas ahí?`,
+            initialValue: false,
+        });
+        if (p.isCancel(proceed) || !proceed) {
+            p.outro("Código actualizado. Corre `npx create-kontrolia-auth migrate` cuando quieras aplicar la base de datos.");
+            return;
+        }
+    }
     const migrated = await migrateWithSpinner(url);
     p.outro(migrated
         ? "Listo. Si despliegas con Docker: `docker compose -f docker/docker-compose.yml up -d --build`. Si usas Vercel/Railway/Render/Coolify, vuelve a desplegar (push a tu rama, o su CLI) para que tomen el código nuevo."
@@ -188,8 +223,11 @@ async function runDeployCommand() {
         serviceRoleKey = await textOrExit("Service role key (server-only, nunca la expongas al navegador)");
     }
     const db = { mode: "existing", databaseUrl: "", supabaseUrl, anonKey, serviceRoleKey };
-    await askDeploymentStep(process.cwd(), db);
-    p.outro("Listo.");
+    const deployment = await askDeploymentStep(process.cwd(), db);
+    openBrowser(deployment.authServerUrl);
+    openBrowser(deployment.adminPanelUrl);
+    p.outro(`Listo. Deberían haberse abierto dos pestañas: ${deployment.authServerUrl} y ${deployment.adminPanelUrl}. ` +
+        "Si no cargan porque el servidor no está corriendo todavía en esa URL, recárgalas una vez que lo esté.");
 }
 /** Default flow: preflight → (scaffold if outside repo) → DB → migrate → app → deploy. */
 async function runInstall(targetDirArg) {
@@ -237,9 +275,13 @@ async function runInstall(targetDirArg) {
     else {
         p.note("Cuando la base de datos esté lista corre `npx create-kontrolia-auth migrate`, y registra tu primera aplicación desde admin-panel.", "Migraciones pendientes");
     }
-    await askDeploymentStep(repoRoot, db);
+    const deployment = await askDeploymentStep(repoRoot, db);
+    openBrowser(deployment.authServerUrl);
+    openBrowser(deployment.adminPanelUrl);
     const cdHint = scaffolded && dirName ? `cd ${dirName} && ` : "";
-    p.outro(`Listo. Arranca en local con \`${cdHint}pnpm dev\`, crea tu primer usuario/organización en /register, y usa @kontrolia/react en tus apps.`);
+    p.outro(`Listo. Deberían haberse abierto dos pestañas — la de inicio de sesión (${deployment.authServerUrl}) y el panel de ` +
+        `administración (${deployment.adminPanelUrl}). Si no cargan porque los servidores aún no están arriba, corre ` +
+        `\`${cdHint}pnpm dev\` y recárgalas. Crea tu primer usuario/organización en /register, y usa @kontrolia/react en tus apps.`);
 }
 async function main() {
     const args = process.argv.slice(2);

package/dist/steps/deployment.d.ts

@@ -1,8 +1,14 @@
 import type { DatabaseAnswer } from "./database.js";
+export type DeployTarget = "docker" | "vercel" | "railway" | "render" | "coolify" | "manual";
 /**
  * Question B from the architecture plan: where do auth-server/admin-panel
  * run? Fully independent from the database question above — this only
  * ever generates env files, it never touches the database connection.
  */
-export declare function askDeploymentStep(repoRoot: string, db: DatabaseAnswer): Promise<void>;
+export interface DeploymentAnswer {
+    authServerUrl: string;
+    adminPanelUrl: string;
+    target: DeployTarget;
+}
+export declare function askDeploymentStep(repoRoot: string, db: DatabaseAnswer): Promise<DeploymentAnswer>;
 //# sourceMappingURL=deployment.d.ts.map

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;AAiLpD;;;;GAIG;AACH,wBAAsB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,EAAE,EAAE,EAAE,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,CAsJ3F"}
+{"version":3,"file":"deployment.d.ts","sourceRoot":"","sources":["../../src/steps/deployment.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,eAAe,CAAC;AAEpD,MAAM,MAAM,YAAY,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,GAAG,QAAQ,GAAG,SAAS,GAAG,QAAQ,CAAC;AA+K7F;;;;GAIG;AACH,MAAM,WAAW,gBAAgB;IAC/B,aAAa,EAAE,MAAM,CAAC;IACtB,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,YAAY,CAAC;CACtB;AAED,wBAAsB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,EAAE,EAAE,EAAE,cAAc,GAAG,OAAO,CAAC,gBAAgB,CAAC,CAwJvG"}

package/dist/steps/deployment.js

@@ -142,11 +142,6 @@ async function tryAutoCreateVercelProjects(repoRoot, authServerEnv, adminPanelEn
     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");
     return false;
 }
-/**
- * Question B from the architecture plan: where do auth-server/admin-panel
- * run? Fully independent from the database question above — this only
- * ever generates env files, it never touches the database connection.
- */
 export async function askDeploymentStep(repoRoot, db) {
     // A previous install/deploy already wrote these into .env.local — reuse
     // them as editable defaults instead of making the user retype the same
@@ -276,4 +271,5 @@ export async function askDeploymentStep(repoRoot, db) {
     if (!autoCreated) {
         p.note(NEXT_STEPS[target], `Despliegue: ${target}`);
     }
+    return { authServerUrl, adminPanelUrl, target };
 }

package/dist/utils/open-browser.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Best-effort browser open, no new dependency (avoids pulling in the `open`
+ * npm package for three lines of platform dispatch). Never throws — a
+ * failed/unsupported open shouldn't fail the installer over a convenience
+ * feature. Callers may open a URL before its server is actually listening
+ * (e.g. right after the wizard finishes, before the user runs `pnpm dev`) —
+ * that's expected; the tab just needs a manual refresh once it's up, same
+ * as most dev-server CLIs that open the browser optimistically.
+ */
+export declare function openBrowser(url: string): void;
+//# sourceMappingURL=open-browser.d.ts.map

package/dist/utils/open-browser.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"open-browser.d.ts","sourceRoot":"","sources":["../../src/utils/open-browser.ts"],"names":[],"mappings":"AAEA;;;;;;;;GAQG;AACH,wBAAgB,WAAW,CAAC,GAAG,EAAE,MAAM,GAAG,IAAI,CAiB7C"}

package/dist/utils/open-browser.js

@@ -0,0 +1,28 @@
+import { spawn } from "node:child_process";
+/**
+ * Best-effort browser open, no new dependency (avoids pulling in the `open`
+ * npm package for three lines of platform dispatch). Never throws — a
+ * failed/unsupported open shouldn't fail the installer over a convenience
+ * feature. Callers may open a URL before its server is actually listening
+ * (e.g. right after the wizard finishes, before the user runs `pnpm dev`) —
+ * that's expected; the tab just needs a manual refresh once it's up, same
+ * as most dev-server CLIs that open the browser optimistically.
+ */
+export function openBrowser(url) {
+    try {
+        const child = process.platform === "win32"
+            ? spawn("cmd", ["/c", "start", "", url], { detached: true, stdio: "ignore", windowsHide: true })
+            : process.platform === "darwin"
+                ? spawn("open", [url], { detached: true, stdio: "ignore" })
+                : spawn("xdg-open", [url], { detached: true, stdio: "ignore" });
+        // Without a listener, a spawn failure (e.g. no xdg-open on a headless
+        // box) is an unhandled 'error' event — Node treats that as fatal and
+        // crashes the CLI right after a successful install. Swallow it: the
+        // URL is always printed as text too, so this is purely a convenience.
+        child.on("error", () => { });
+        child.unref();
+    }
+    catch {
+        // Best-effort only.
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-kontrolia-auth",
-  "version": "2.4.2",
+  "version": "2.4.4",
   "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": [
@@ -35,7 +35,7 @@
   "dependencies": {
     "@clack/prompts": "^0.9.1",
     "jose": "^5.9.6",
-    "@kontrolia/db": "2.1.0"
+    "@kontrolia/db": "2.1.2"
   },
   "devDependencies": {
     "@types/node": "^22.10.2",