@magentrix-corp/magentrix-cli 1.3.3 → 1.3.4

package/README.md

@@ -503,17 +503,19 @@ magentrix vue-build-stage
 
 #### Vue Development Server
 ```bash
-magentrix iris-dev
+magentrix run-dev
 ```
 **What it does**: Starts the Vue development server with platform assets (CSS, fonts) automatically injected from your Magentrix instance.
 
+**Authentication**: Uses `VITE_REFRESH_TOKEN` from `.env.development` (no CLI authentication required). This command can be run inside the Vue project directory.
+
 **Options:**
 - `--path <dir>` - Specify Vue project path
 - `--no-inject` - Skip asset injection, just run dev server
 - `--restore` - Restore `.env.development` from backup without running
 
 **Process:**
-1. Fetch platform assets from Magentrix
+1. Fetch platform assets from Magentrix using `.env.development` credentials
 2. Backup `.env.development` and inject assets
 3. Run `npm run dev`
 4. Restore `.env.development` on exit (Ctrl+C)
@@ -577,7 +579,7 @@ export const config = {
 ```bash
 VITE_SITE_URL = https://yourinstance.magentrix.com
 VITE_REFRESH_TOKEN = your-api-key
-VITE_ASSETS = '[]'  # Injected automatically by iris-dev
+VITE_ASSETS = '[]'  # Injected automatically by run-dev
 ```
 
 **Accepted field names in config.ts:**
@@ -586,6 +588,19 @@ VITE_ASSETS = '[]'  # Injected automatically by iris-dev
 - Description: `appDescription` or `app_description`
 - Icon: `appIconId` or `app_icon_id`
 
+### Command Availability
+
+**In Vue project directories** (detected by presence of `config.ts`):
+- ✓ `magentrix iris-link` - Link project to CLI
+- ✓ `magentrix run-dev` - Start dev server (uses `.env.development` credentials)
+- ✓ `magentrix vue-build-stage` - Build and stage
+
+**In Magentrix workspace directories** (has `.magentrix/` folder):
+- ✓ All standard commands (`setup`, `pull`, `publish`, etc.)
+- ✓ All Iris commands (`iris-delete`, `iris-recover`, etc.)
+
+**Note**: Commands like `pull`, `publish`, `autopublish` require a Magentrix workspace and will show an error if run inside a Vue project directory.
+
 ### Typical Development Workflow
 
 ```bash
@@ -593,7 +608,7 @@ VITE_ASSETS = '[]'  # Injected automatically by iris-dev
 magentrix iris-link           # Link your Vue project
 
 # Development
-magentrix iris-dev            # Start dev server with platform assets
+magentrix run-dev             # Start dev server with platform assets
 # Make changes, test locally
 # Press Ctrl+C to stop
 
@@ -1058,7 +1073,7 @@ magentrix status        # Shows sync status
 - `magentrix update` - Update to latest version
 - `magentrix iris-link` - Link Vue.js projects for deployment
 - `magentrix vue-build-stage` - Build and stage Vue.js apps
-- `magentrix iris-dev` - Start Vue dev server with platform assets
+- `magentrix run-dev` - Start Vue dev server with platform assets
 - `magentrix iris-delete` - Delete an Iris app with recovery backup
 - `magentrix iris-recover` - Recover a deleted Iris app
 
@@ -1072,6 +1087,6 @@ Once you're comfortable with basic usage:
 2. **Learn the autopublish workflow** for faster development
 3. **Explore conflict resolution** if you work in a team
 4. **Check out templates** created by the `create` command to understand best practices
-5. **Deploy Vue.js apps** using `iris-link`, `vue-build-stage`, and `iris-dev` commands
+5. **Deploy Vue.js apps** using `iris-link`, `vue-build-stage`, and `run-dev` commands
 
 Happy coding with MagentrixCLI! 🚀

package/actions/iris/dev.js

@@ -20,15 +20,16 @@ import {
 } from '../../utils/iris/linker.js';
 
 /**
- * iris-dev command - Start Vue dev server with platform assets injected.
+ * run-dev command - Start Vue dev server with platform assets injected.
  *
- * Assets are injected into .env.development (if exists) or config.ts.
- * The modified file is backed up and restored when the dev server exits.
+ * Uses credentials from .env.development (VITE_REFRESH_TOKEN, VITE_SITE_URL).
+ * Assets are injected into .env.development only.
+ * The .env.development file is backed up and restored when the dev server exits.
  *
  * Options:
  *   --path <dir>      Specify Vue project path
  *   --no-inject       Skip asset injection, just run dev server
- *   --restore         Restore .env.development or config.ts from backup
+ *   --restore         Restore .env.development from backup
  */
 export const irisDev = async (options = {}) => {
     process.stdout.write('\x1Bc'); // Clear console
@@ -173,12 +174,13 @@ export const irisDev = async (options = {}) => {
  */
 async function runDevServer(projectPath, modifiedFilePath, modifiedFileName, backupPath, assetsInjected) {
     return new Promise((resolvePromise) => {
-        const npmCmd = process.platform === 'win32' ? 'npm.cmd' : 'npm';
+        const isWindows = process.platform === 'win32';
+        const npmCmd = isWindows ? 'npm.cmd' : 'npm';
 
         const child = spawn(npmCmd, ['run', 'dev'], {
             cwd: projectPath,
             stdio: 'inherit',
-            shell: false
+            shell: isWindows  // Windows requires shell: true for .cmd files
         });
 
         // Handle cleanup on exit
@@ -316,7 +318,7 @@ async function selectProject() {
         console.log();
         console.log(chalk.gray('To get started:'));
         console.log(chalk.white(`  1. Link a Vue project: ${chalk.cyan('magentrix iris-link')}`));
-        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix iris-dev --path /path/to/vue-project')}`));
+        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix run-dev --path /path/to/vue-project')}`));
         console.log();
     }
 

package/bin/magentrix.js

@@ -44,7 +44,7 @@ function requireMagentrixWorkspace(fn) {
             console.error(chalk.gray('This command requires a Magentrix workspace with global API key and instance URL.\n'));
             console.error(chalk.cyan('Available commands in Vue projects:'));
             console.error(chalk.gray('  • magentrix iris-link'));
-            console.error(chalk.gray('  • magentrix iris-dev'));
+            console.error(chalk.gray('  • magentrix run-dev'));
             console.error(chalk.gray('  • magentrix vue-build-stage\n'));
             process.exit(1);
         }
@@ -105,7 +105,7 @@ program
                 { name: 'update', desc: 'Update MagentrixCLI to the latest version', icon: '⬆️  ' },
                 { name: 'iris-link', desc: 'Link a Vue project to the CLI', icon: '🔗 ' },
                 { name: 'vue-build-stage', desc: 'Build Vue project and stage for publish', icon: '🏗️  ' },
-                { name: 'iris-dev', desc: 'Start Vue dev server with platform assets', icon: '🌐 ' },
+                { name: 'run-dev', desc: 'Start Vue dev server with platform assets', icon: '🌐 ' },
                 { name: 'iris-delete', desc: 'Delete an Iris app with backup', icon: '🗑️  ' },
                 { name: 'iris-recover', desc: 'Recover a deleted Iris app from backup', icon: '♻️  ' }
             ];
@@ -254,7 +254,7 @@ program
     .action(vueBuildStage);
 
 program
-    .command('iris-dev')
+    .command('run-dev')
     .description('Start Vue dev server with platform assets injected')
     .option('--path <path>', 'Path to the Vue project')
     .option('--no-inject', 'Skip asset injection')
@@ -282,7 +282,7 @@ program.argument('[command]', 'command to run').action((cmd) => {
             console.error(chalk.gray('This command requires a Magentrix workspace with global API key and instance URL.\n'));
             console.error(chalk.cyan('Available commands in Vue projects:'));
             console.error(chalk.gray('  • magentrix iris-link'));
-            console.error(chalk.gray('  • magentrix iris-dev'));
+            console.error(chalk.gray('  • magentrix run-dev'));
             console.error(chalk.gray('  • magentrix vue-build-stage\n'));
             process.exit(1);
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@magentrix-corp/magentrix-cli",
-  "version": "1.3.3",
+  "version": "1.3.4",
   "description": "CLI tool for synchronizing local files with Magentrix cloud platform",
   "main": "index.js",
   "type": "module",