@tgcloud/cli 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgcloud/cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "CLI for the Telegram serverless platform",
   "keywords": [
     "telegram",

package/src/commands/deploy.js

@@ -190,14 +190,23 @@ export function registerDeploy(program) {
       }
 
       // 4. Send the batch (with automatic re-auth on 401/403).
+      // One "Deploying N changes..." line carries both phases: the spinner shows
+      // it live during the request, then (once ora has erased the spinner line)
+      // we reprint it persistently as the header above the ✓ results. This keeps
+      // a labeled separator between the "what will change" preview and the "what
+      // happened" results — without it the two file lists butt together and read
+      // as the same paths twice — while avoiding a second, redundant activity
+      // line. Count includes deletions, so it matches the results below.
+      const changeCount = changedPaths.length + deletedPaths.length;
+      const deployingLine = `Deploying ${changeCount} change${changeCount === 1 ? '' : 's'}...`;
+      console.log(''); // blank line stays put whether or not the spinner renders
+
       const startTime = Date.now();
       let response;
       try {
         response = await retryOnAuthError(async () => {
           const token = await resolveToken();
-          const spinner = createSpinner(
-            `Deploying ${changedPaths.length} change${changedPaths.length === 1 ? '' : 's'}...`
-          );
+          const spinner = createSpinner(deployingLine);
           spinner.start();
           try {
             const r = await batchDeploy(token, { expected_revision, manifest, changed_sources });
@@ -219,6 +228,7 @@ export function registerDeploy(program) {
         process.exit(1);
       }
 
+      console.log(deployingLine); // persistent header (spinner line was erased on stop)
       for (const p of changedPaths) done(p);
       for (const p of deletedPaths) done(p, 'deleted');
 

package/src/commands/init.js

@@ -213,11 +213,11 @@ export function registerInit(program) {
 
       // "Project ready" + the files note is always init's — it owns the scaffold,
       // so the description stays here (generic, no hardcoded names, survives new
-      // directories the platform may add). Only the numbered "Next steps" is suppressed
-      // when a bootstrap (create-bot) delegates and sets TGCLOUD_INIT_QUIET_NEXT:
-      // it prints its own, leading with `cd` and using npx.
+      // directories the platform may add). The "Next steps" block is suppressed
+      // when create-bot delegates; it prints its own. TGCLOUD_INIT_QUIET_NEXT is
+      // the legacy flag name, read for back-compat with an older cached create-bot.
       info('\nProject ready. The scaffolded files are a starting point — edit or delete as you like.');
-      if (!process.env.TGCLOUD_INIT_QUIET_NEXT) {
+      if (!process.env.TGCLOUD_VIA_CREATE && !process.env.TGCLOUD_INIT_QUIET_NEXT) {
         info('\nNext steps:');
         info(`  ${chalk.cyan('tgcloud login')}   ${chalk.dim('# link this project to a bot')}`);
         info(`  ${chalk.cyan('tgcloud push')}    ${chalk.dim('# deploy to the cloud')}`);

package/src/core/credentials.js

@@ -138,7 +138,16 @@ function isValidFormat(token) {
  * Loops on invalid input until the user provides a working token or aborts (Ctrl-C).
  */
 export async function loginInteractive() {
-  console.log('Link this project to a bot.');
+  // create-bot already asked "Link your bot now?" right before delegating here,
+  // so repeating the "Link this project to a bot." intro is redundant. Under the
+  // create-bot bootstrap (TGCLOUD_VIA_CREATE) drop the intro and lead with a blank
+  // line so the token instructions get some room under the prompt above.
+  // Standalone `tgcloud login` keeps the intro.
+  if (process.env.TGCLOUD_VIA_CREATE) {
+    console.log('');
+  } else {
+    console.log('Link this project to a bot.');
+  }
   console.log('Get your CLI access token from @BotFather: your bot → Serverless → CLI Access → Access token.');
 
   while (true) {