at-builder 1.3.3 → 1.4.0

package/README.md

@@ -58,16 +58,16 @@ atb deploy
 
 ### **Core Commands**
 
-| Command | Description | Options |
-|---------|-------------|---------|
-| `atb init` | Initialize project with configuration files | |
-| `atb new` | Create new Adobe Target activity with variations | |
-| `atb build` | Build activity for development | `--prod` for production |
-| `atb dev` | Start development server with file watching | `--browser` to open browser |
-| `atb deploy` | Deploy activity to Adobe Target | `--dry-run` for testing, `--force` to override the 60s cooldown |
-| `atb sync` | Sync `build.config.json` with the AT activity (pages, experiences, names) | `--scaffold` to auto-create missing variation folders |
-| `atb doctor` | Diagnose and fix configuration issues | `--fix` to auto-fix |
-| `atb install-extension` | Install the bundled at-builder VSCode extension (.vsix) | `--editor cursor` (or `codium`, etc.) to use a non-VSCode editor CLI |
+| Command                 | Description                                                               | Options                                                              |
+| ----------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------- |
+| `atb init`              | Initialize project with configuration files                               |                                                                      |
+| `atb new`               | Create new Adobe Target activity with variations                          |                                                                      |
+| `atb build`             | Build activity for development                                            | `--prod` for production                                              |
+| `atb dev`               | Start development server with file watching                               | `--browser` to open browser                                          |
+| `atb deploy`            | Deploy activity to Adobe Target                                           | `--dry-run` for testing, `--force` to override the 60s cooldown      |
+| `atb sync`              | Sync `build.config.json` with the AT activity (pages, experiences, names) | `--scaffold` to auto-create missing variation folders                |
+| `atb doctor`            | Diagnose and fix configuration issues                                     | `--fix` to auto-fix                                                  |
+| `atb install-extension` | Install the at-builder VSCode extension from the Marketplace             | `--editor cursor` (or `codium`, etc.) to use a non-VSCode editor CLI |
 
 ### **Examples**
 
@@ -156,7 +156,7 @@ VARIATION="Variation-1"
 # Adobe Target Deployment
 ADOBE_CLIENT_ID="your-client-id"
 ADOBE_CLIENT_SECRET="your-client-secret"
-ADOBE_TENANT=""           # Optional. Your Adobe org slug (e.g. "ups"). Enables clickable AT UI links in deploy/sync output.
+ADOBE_TENANT=""           # Optional. Your Adobe org slug (e.g."tst123"). Enables clickable AT UI links in deploy/sync output.
 ```
 
 ### **Adobe Target Configuration (adobe.config.js)**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "at-builder",
-    "version": "1.3.3",
+    "version": "1.4.0",
     "main": "bin/index.js",
     "bin": {
         "atb": "bin/index.js"

package/src/constants/config.ts

@@ -76,7 +76,7 @@ ${formatText("COMMANDS", 'yellow', true)}
     ${formatText("sync --scaffold", 'cyan', true)}  Sync and auto-create any missing variation folders with boilerplate
     ${formatText("doctor", 'cyan', true)}         Diagnose and fix project configuration issues
     ${formatText("doctor --fix", 'cyan', true)}   Automatically fix detected configuration issues
-    ${formatText("install-extension", 'cyan', true)}  Install the bundled at-builder VSCode extension (.vsix)
+    ${formatText("install-extension", 'cyan', true)}  Install the at-builder VSCode extension from the Marketplace
     
 ${formatText("GLOBAL OPTIONS", 'yellow', true)}
     ${formatText("-v, --verbose", 'green')}       Enable detailed logging

package/src/index.ts

@@ -113,7 +113,7 @@ const setupCommander = async () => {
 
     program
         .command('install-extension')
-        .description('Install the bundled at-builder VSCode extension (.vsix)')
+        .description('Install the at-builder VSCode extension from the Marketplace')
         .option('--editor <bin>', 'Editor CLI to use (e.g. code, cursor, codium)', 'code')
         .action(async (options, command) => {
             const globalOpts = command.parent.opts();
@@ -246,45 +246,23 @@ const handleSync = async (scaffold: boolean, verbose: boolean): Promise<void> =>
 /**
  * Handles the install-extension command.
  *
- * Locates the bundled at-builder-*.vsix in at-builder's install directory
- * (one level up from this compiled file) and installs it via the editor's
- * CLI. Defaults to `code`; users on Cursor/VSCodium can pass --editor.
- *
- * The .vsix lives inside the at-builder package itself, NOT the consumer's
- * project — so it resolves via __dirname, not PWD.
+ * Installs the at-builder VSCode extension from the VS Code Marketplace
+ * using the editor's CLI. Defaults to `code`; users on Cursor/VSCodium
+ * can pass --editor.
  */
 const handleInstallExtension = async (editor: string, verbose: boolean): Promise<void> => {
-    if (verbose) logger.info("verbose", `Installing VSCode extension via ${editor}`);
-
-    const installRoot = path.join(__dirname, "..");
+    const extensionId = "UpendraSengar.at-builder";
 
-    let candidates: string[];
-    try {
-        candidates = fs.readdirSync(installRoot)
-            .filter(f => /^at-builder-.+\.vsix$/.test(f))
-            .sort()
-            .reverse(); // latest version first by lexicographic sort
-    } catch (error) {
-        console.error(`❌ Failed to scan at-builder directory: ${error.message}`);
-        process.exit(1);
-    }
-
-    if (candidates.length === 0) {
-        console.error("❌ No at-builder VSCode extension (.vsix) found bundled with this install.");
-        console.error(`💡 Expected at: ${installRoot}/at-builder-*.vsix`);
-        process.exit(1);
-    }
+    if (verbose) logger.info("verbose", `Installing ${extensionId} via ${editor}`);
 
-    const vsixPath = path.join(installRoot, candidates[0]);
-    console.log(`📦 Installing ${candidates[0]} via "${editor}"...`);
+    console.log(`📦 Installing ${extensionId} from the Marketplace via "${editor}"...`);
 
-    const result = spawn(editor, ["--install-extension", vsixPath], {
+    const result = spawn(editor, ["--install-extension", extensionId], {
         stdio: "inherit",
         shell: true
     });
 
     result.on("error", (err) => {
-        // ENOENT here means the editor binary isn't on PATH.
         if ((err as NodeJS.ErrnoException).code === "ENOENT") {
             console.error(`❌ "${editor}" CLI not found in PATH.`);
             if (editor === "code") {
@@ -303,8 +281,6 @@ const handleInstallExtension = async (editor: string, verbose: boolean): Promise
             console.log("✅ Extension installed. Reload your editor window to activate.");
             return;
         }
-        // 127 = shell's "command not found". With shell:true the spawn 'error'
-        // event never fires for missing CLIs, so we surface the same hint here.
         if (code === 127) {
             console.error(`❌ "${editor}" CLI not found in PATH.`);
             if (editor === "code") {