stackpatch 1.1.5 → 1.1.6

package/README.md

@@ -72,19 +72,23 @@ The CLI will guide you through an interactive setup:
 ### Create New Project
 
 ```bash
-# Using npm create (recommended)
-npm create stackpatch@latest my-app
-
-# Using npx
-npx create-stackpatch@latest my-app
-# or
+# Using npx (recommended - works immediately)
 npx stackpatch create my-app
 
+# Or without project name (will prompt)
+npx stackpatch create
+
+# Using npm create (requires package to be published)
+npm create stackpatch@latest my-app
+
 # Using bunx (Bun's npx equivalent)
 bunx create-stackpatch@latest my-app
 ```
 
-> **Note:** All commands will prompt you for a project name if not provided.
+> **Note:**
+> - `npx stackpatch create` works immediately and doesn't require the package to be published
+> - `npm create` and `npx create-stackpatch@latest` require the package to be published to npm first
+> - All commands will prompt you for a project name if not provided
 
 ### Revert an Installation
 

package/bin/stackpatch.js

@@ -0,0 +1,79 @@
+#!/usr/bin/env node
+/**
+ * StackPatch CLI Wrapper
+ *
+ * This wrapper detects the runtime (Bun or Node.js) and executes the TypeScript file accordingly.
+ * - If Bun is available, uses Bun directly (faster)
+ * - Otherwise, uses tsx for Node.js compatibility
+ */
+
+import { spawn, spawnSync } from "child_process";
+import { fileURLToPath } from "url";
+import { dirname, join } from "path";
+import { existsSync } from "fs";
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+const tsFile = join(__dirname, "stackpatch.ts");
+
+// Check if Bun is available
+function hasBun() {
+  try {
+    const result = spawnSync("bun", ["--version"], {
+      stdio: "ignore",
+      timeout: 1000,
+    });
+    return result.status === 0;
+  } catch {
+    return false;
+  }
+}
+
+// Execute with appropriate runtime
+const args = process.argv.slice(2);
+
+if (hasBun()) {
+  // Use Bun if available
+  const bun = spawn("bun", [tsFile, ...args], {
+    stdio: "inherit",
+    cwd: process.cwd(),
+  });
+  bun.on("exit", (code) => process.exit(code || 0));
+} else {
+  // Use tsx for Node.js
+  // Try multiple possible locations for tsx
+  const possibleTsxPaths = [
+    join(__dirname, "../node_modules/.bin/tsx"), // Local installation
+    join(__dirname, "../../node_modules/.bin/tsx"), // Monorepo structure
+    join(process.cwd(), "node_modules/.bin/tsx"), // Project's node_modules
+  ];
+
+  let tsxPath = null;
+  for (const path of possibleTsxPaths) {
+    if (existsSync(path)) {
+      tsxPath = path;
+      break;
+    }
+  }
+
+  if (tsxPath) {
+    const tsx = spawn(tsxPath, [tsFile, ...args], {
+      stdio: "inherit",
+      cwd: process.cwd(),
+    });
+    tsx.on("exit", (code) => process.exit(code || 0));
+  } else {
+    // Fallback: try tsx from PATH or use npx
+    const tsx = spawn("npx", ["-y", "tsx", tsFile, ...args], {
+      stdio: "inherit",
+      cwd: process.cwd(),
+    });
+    tsx.on("exit", (code) => {
+      if (code !== 0) {
+        console.error("Error: Could not execute TypeScript file. Please ensure tsx is available.");
+        process.exit(1);
+      }
+      process.exit(code || 0);
+    });
+  }
+}

package/bin/stackpatch.ts

@@ -1,4 +1,7 @@
-#!/usr/bin/env bun
+#!/usr/bin/env tsx
+// This file works with both Bun and Node.js
+// - Bun can execute TypeScript files directly
+// - Node.js uses tsx (installed as dependency) to execute TypeScript
 
 import fs from "fs";
 import path from "path";
@@ -9,9 +12,9 @@ import { spawnSync } from "child_process";
 import Jimp from "jimp";
 
 // ---------------- CONFIG ----------------
-// Get directory path - Bun supports import.meta.dir
-// @ts-expect-error - Bun-specific API, not in Node types
-const CLI_DIR = import.meta.dir || path.dirname(new URL(import.meta.url).pathname);
+// Get directory path - Works with both Bun and Node.js
+// Bun has import.meta.dir, Node.js doesn't - use fallback
+const CLI_DIR = (import.meta as any).dir || path.dirname(new URL(import.meta.url).pathname);
 // Resolve boilerplate path - use local boilerplate inside CLI package
 const BOILERPLATE_ROOT = path.resolve(CLI_DIR, "../boilerplate");
 const PATCHES: Record<

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "stackpatch",
-  "version": "1.1.5",
+  "version": "1.1.6",
   "description": "Composable frontend features for modern React & Next.js apps - Add authentication, UI components, and more with zero configuration",
   "main": "bin/stackpatch.ts",
   "type": "module",
   "bin": {
-    "stackpatch": "bin/stackpatch.ts",
-    "create-stackpatch": "bin/stackpatch.ts"
+    "stackpatch": "bin/stackpatch.js",
+    "create-stackpatch": "bin/stackpatch.js"
   },
   "files": [
     "bin",
@@ -47,6 +47,7 @@
   },
   "homepage": "https://github.com/Darshh09/StackPatch#readme",
   "engines": {
+    "node": ">=18.0.0",
     "bun": ">=1.0.0"
   },
   "packageManager": "pnpm@10.28.0",