kasy-cli 1.21.0 → 1.21.2

package/lib/utils/checks.js

@@ -32,7 +32,11 @@ function getInstallGuide(tool) {
   const guides = {
     gcloud: {
       darwin: { cmd: 'brew install --cask google-cloud-sdk', after: 'gcloud auth login', url: 'https://cloud.google.com/sdk/docs/install' },
-      win32: { cmd: 'winget install --id Google.CloudSDK -e', after: 'gcloud auth login', url: 'https://cloud.google.com/sdk/docs/install-sdk#windows' },
+      // The accept flags are required for a NON-interactive winget run — without
+      // them winget stalls waiting for the user to accept the source/package
+      // agreements (which is why the silent auto-install failed). They're also
+      // harmless when the user runs the command by hand.
+      win32: { cmd: 'winget install --id Google.CloudSDK -e --accept-source-agreements --accept-package-agreements', after: 'gcloud auth login', url: 'https://cloud.google.com/sdk/docs/install-sdk#windows' },
       linux: { cmd: 'curl https://sdk.cloud.google.com | bash', after: 'gcloud auth login', url: 'https://cloud.google.com/sdk/docs/install' },
     },
     flutter: {
@@ -88,7 +92,16 @@ const PLATFORM_CHECKS = {
   linux: []
 };
 
-/** Firebase CLI + FlutterFire — required for push notifications (FCM) on all backends */
+/**
+ * Firebase CLI + FlutterFire — required for push notifications (FCM) on EVERY
+ * backend (Firebase, Supabase, API), since FCM is the shared push layer.
+ *
+ * gcloud is deliberately NOT in this list. It's only needed to create a Firebase
+ * project FROM SCRATCH (an opt-in path), so checking it for every backend made
+ * the Supabase/API setup offer to install gcloud for no reason — and the user
+ * doesn't even need it there. The create-from-scratch flow verifies gcloud on
+ * its own (checkGcloudAuth in new.js), exactly when it's actually required.
+ */
 const FIREBASE_CHECKS = [
   {
     name: 'Firebase CLI',
@@ -109,22 +122,6 @@ const FIREBASE_CHECKS = [
     pubGlobalBin: 'flutterfire',
     tryInstallMessageKey: 'setup.flutterfire.installing',
   },
-  {
-    name: 'gcloud CLI (create-from-scratch)',
-    command: 'gcloud --version',
-    required: false,
-    installGuide: () => getInstallGuide('gcloud'),
-    confirmInstall: true,
-    waitPromptKey: 'checks.waitPrompt.gcloud.install',
-  },
-  {
-    name: 'gcloud auth (create-from-scratch)',
-    command: 'gcloud auth print-access-token',
-    required: false,
-    showVersion: false,
-    failHint: 'gcloud auth login',
-    waitPromptKey: 'checks.waitPrompt.gcloud.auth',
-  },
 ];
 
 const BACKEND_CHECKS = {
@@ -231,6 +228,7 @@ async function runSingleCheck(check, options = {}) {
   // Lightweight auto-install (npm / pub global). Heavy tools (gcloud, flutter)
   // use confirmInstall and are handled interactively after the spinner.
   if (check.tryInstall) {
+    if (typeof options.onInstalling === 'function') options.onInstalling(check);
     const installed = await execTool(check.tryInstall, INSTALL_TIMEOUT);
     if (installed.ok) {
       const verified = await verifyTool(check);
@@ -267,8 +265,7 @@ async function revalidate(check, t) {
  * Returns true if the tool is present by the end.
  */
 async function recoverCheckInteractively(check, t) {
-  ui.log.warn(`${check.name} ${t('checks.notFound.short') || 'not found'}`);
-
+  // The step list already flagged this tool as missing; go straight to fixing it.
   const guide = typeof check.installGuide === 'function' ? check.installGuide() : null;
 
   // 1) Offer auto-install for heavy tools that have a package-manager command.
@@ -278,12 +275,17 @@ async function recoverCheckInteractively(check, t) {
       initialValue: true,
     });
     if (doInstall) {
-      const spinner = ui.spinner();
+      const spinner = ui.timedSpinner();
       spinner.start(t('checks.install.running', { name: check.name }));
       const installed = await execTool(guide.cmd, INSTALL_TIMEOUT);
       spinner.stop(t('checks.install.running', { name: check.name }));
       if (installed.ok && (await revalidate(check, t))) return true;
       ui.log.warn(t('checks.install.failedManual', { name: check.name }));
+      // Surface the installer's own last line — it usually says WHY (needs admin,
+      // agreement not accepted, package not found), which beats a generic failure.
+      const reason = (installed.stderr || installed.error || '')
+        .split('\n').map((l) => l.trim()).filter(Boolean).pop();
+      if (reason) ui.log.message(kleur.dim(reason.slice(0, 200)));
     }
   }
 
@@ -350,32 +352,38 @@ async function runChecks(checks, title, options = {}) {
   // command never blocks waiting for input that will never come.
   const interactive = options.interactive !== false && Boolean(process.stdout.isTTY);
 
-  // Single spinner over all checks, show failures afterwards. The visual
-  // sits inside the clack rail (│) opened by the caller's ui.intro().
-  const { spinnerLabel = title, doneLabel = title } = options;
-  const spinner = ui.spinner();
-  spinner.start(spinnerLabel);
-
+  // One step per tool, each with its own running clock — so the user always
+  // sees WHAT is being checked or installed, and that it's still moving. This
+  // replaces the single frozen "…" spinner that looked stuck during long
+  // installs (e.g. FlutterFire). Same stepper the kasy-new flow uses, so the
+  // environment setup feels as guided as the project generation, on every OS.
+  const stepper = ui.makeTimedStepper();
   const results = [];
+
   for (const check of checks) {
-    results.push(await runSingleCheck({ ...check, t }, { showVersion }));
+    stepper.next(t('checks.checking', { name: check.name }));
+    const result = await runSingleCheck({ ...check, t }, {
+      showVersion,
+      // Switch the line to "Installing X…" while the auto-install runs, so the
+      // clock keeps ticking against a message that explains the wait.
+      onInstalling: (c) => stepper.update(
+        c.tryInstallMessageKey ? t(c.tryInstallMessageKey) : t('setup.installingNamed', { name: c.name }),
+      ),
+    });
+    results.push(result);
+
+    if (result.ok) {
+      stepper.succeed(result.version ? `${result.name} — ${result.version}` : result.name);
+    } else if (result.required) {
+      const detail = result.autoInstallFailed ? ` — ${t('checks.install.failed')}` : '';
+      stepper.fail(`${t('checks.missing', { name: result.name })}${detail}`);
+    } else {
+      stepper.warn(t('checks.notFound', { name: result.name }));
+    }
   }
 
   const failures = results.filter((r) => !r.ok);
-  const requiredFailures = failures.filter((r) => r.required);
-
-  if (failures.length === 0) {
-    spinner.stop(doneLabel);
-    return results;
-  }
-
-  // Close the spinner reflecting what actually happened: red ▲ if a required
-  // check failed, default green ✦ if only optional checks failed (warnings).
-  if (requiredFailures.length > 0) {
-    spinner.error(doneLabel);
-  } else {
-    spinner.stop(doneLabel);
-  }
+  if (failures.length === 0) return results;
 
   for (const result of failures) {
     if (interactive && canRecover(result)) {
@@ -383,8 +391,10 @@ async function runChecks(checks, title, options = {}) {
       if (recovered) {
         const idx = results.indexOf(result);
         if (idx >= 0) results[idx] = { ...result, ok: true, autoInstallFailed: false };
-        continue;
       }
+      // recoverCheckInteractively already printed the outcome/guidance — don't
+      // duplicate it. The step line above already showed the missing status.
+      continue;
     }
     printCheckFailure(result, t);
   }

package/lib/utils/env-tools.js

@@ -70,14 +70,31 @@ function pubCacheBin(name) {
 }
 
 /**
- * A copy of process.env with `extraDirs` (plus the pub-cache bin) prepended to
- * PATH, so child processes can find tools installed earlier in this same run.
- * On Windows we set both `PATH` and `Path` because Node reads the original key.
+ * Well-known install dirs of tools that may not be on the frozen session PATH
+ * yet — e.g. the Google Cloud SDK right after it's installed mid-run. Only
+ * returns dirs that actually exist. Windows-focused (on Unix these tools land
+ * on PATH via the shell profile, which a new terminal already picks up).
+ */
+function extraToolDirs() {
+  if (!isWindows) return [];
+  const candidates = [
+    process.env.LOCALAPPDATA && path.win32.join(process.env.LOCALAPPDATA, 'Google', 'Cloud SDK', 'google-cloud-sdk', 'bin'),
+    process.env.ProgramFiles && path.win32.join(process.env.ProgramFiles, 'Google', 'Cloud SDK', 'google-cloud-sdk', 'bin'),
+    process.env['ProgramFiles(x86)'] && path.win32.join(process.env['ProgramFiles(x86)'], 'Google', 'Cloud SDK', 'google-cloud-sdk', 'bin'),
+  ].filter(Boolean);
+  return candidates.filter((dir) => fs.existsSync(dir));
+}
+
+/**
+ * A copy of process.env with `extraDirs` (plus the pub-cache bin and known tool
+ * dirs) prepended to PATH, so child processes can find tools installed earlier
+ * in this same run. On Windows we set both `PATH` and `Path` because Node reads
+ * the original key.
  *
  * @param {string[]} [extraDirs] additional directories to expose
  */
 function augmentedEnv(extraDirs = []) {
-  const dirs = [pubCacheBinDir(), ...extraDirs].filter(Boolean);
+  const dirs = [pubCacheBinDir(), ...extraToolDirs(), ...extraDirs].filter(Boolean);
   const env = { ...process.env };
   // Windows env keys are case-insensitive; find whichever key holds PATH.
   const pathKey = Object.keys(env).find((k) => k.toLowerCase() === 'path') || 'PATH';

package/lib/utils/i18n/messages-en.js

@@ -73,7 +73,8 @@ module.exports = {
     'setup.checks.backend': 'Backend checks ({backend})',
     'setup.firebase.installing': 'Installing Firebase CLI...',
     'setup.supabase.installing': 'Installing Supabase CLI...',
-    'setup.flutterfire.installing': 'Installing FlutterFire CLI...',
+    'setup.flutterfire.installing': 'Installing FlutterFire CLI… (may take 1-2 min)',
+    'setup.installingNamed': 'Installing {name}…',
     'setup.warn.hang': 'If setup stalls, run manually: flutterfire --version',
     'setup.warn.supabase': 'Using Supabase or custom API? Firebase still helps with push notifications and remote config.',
     'doctor.title': 'Kasy Doctor',

package/lib/utils/i18n/messages-es.js

@@ -73,7 +73,8 @@ module.exports = {
     'setup.checks.backend': 'Verificaciones de backend ({backend})',
     'setup.firebase.installing': 'Instalando Firebase CLI...',
     'setup.supabase.installing': 'Instalando Supabase CLI...',
-    'setup.flutterfire.installing': 'Instalando FlutterFire CLI...',
+    'setup.flutterfire.installing': 'Instalando FlutterFire CLI… (puede tardar 1-2 min)',
+    'setup.installingNamed': 'Instalando {name}…',
     'setup.warn.hang': 'Si se cuelga, ejecuta manualmente: flutterfire --versión',
     'setup.warn.supabase': '¿Usas Supabase o API propia? Firebase sigue siendo útil para push y remote config.',
     'doctor.title': 'Kasy Doctor',

package/lib/utils/i18n/messages-pt.js

@@ -73,7 +73,8 @@ module.exports = {
     'setup.checks.backend': 'Verificações de backend ({backend})',
     'setup.firebase.installing': 'Instalando Firebase CLI...',
     'setup.supabase.installing': 'Instalando Supabase CLI...',
-    'setup.flutterfire.installing': 'Instalando FlutterFire CLI...',
+    'setup.flutterfire.installing': 'Instalando FlutterFire CLI… (pode levar 1-2 min)',
+    'setup.installingNamed': 'Instalando {name}…',
     'setup.warn.hang': 'Se travar, execute manualmente: flutterfire --version',
     'setup.warn.supabase': 'Usando Supabase ou API propria? O Firebase ainda ajuda com push e remote config.',
     'doctor.title': 'Kasy Doctor',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kasy-cli",
-  "version": "1.21.0",
+  "version": "1.21.2",
   "description": "CLI for scaffolding production-ready Flutter SaaS apps with Firebase, Supabase, or API REST backends.",
   "bin": {
     "kasy": "./bin/kasy.js"