@revkeen/cli-binary 0.1.1 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@revkeen/cli-binary",
-  "version": "0.1.1",
+  "version": "0.2.1",
   "description": "RevKeen CLI — manage payments, subscriptions & billing from your terminal",
   "bin": {
     "revkeen": "run.js"
@@ -11,7 +11,8 @@
   "files": [
     "install.js",
     "run.js",
-    "bin/"
+    "bin/LICENSE",
+    "bin/README.md"
   ],
   "os": [
     "darwin",

package/run.js

@@ -4,10 +4,25 @@
 
 const { execFileSync } = require("child_process");
 const path = require("path");
+const { existsSync } = require("fs");
 
 const binaryName = process.platform === "win32" ? "revkeen.exe" : "revkeen";
 const binaryPath = path.join(__dirname, "bin", binaryName);
 
+// The binary is not published; install.js fetches the right one for this platform
+// at postinstall. Absent means postinstall was skipped (npm install
+// --ignore-scripts) or it failed, and a raw ENOENT from execFileSync says none of
+// that.
+if (!existsSync(binaryPath)) {
+  console.error(`revkeen: no binary at ${binaryPath}.
+
+It is downloaded when this package is installed, so this usually means install
+scripts were skipped (npm install --ignore-scripts) or the download failed.
+
+Fetch it with:  node ${path.join(__dirname, "install.js")}`);
+  process.exit(1);
+}
+
 try {
   execFileSync(binaryPath, process.argv.slice(2), { stdio: "inherit" });
 } catch (err) {