uniner-cli 1.0.2 → 1.0.5

package/bin/uniner-cli.js

@@ -1,42 +1,42 @@
-#!/usr/bin/env node
-// Tiny launcher: forward every CLI invocation to the real PyInstaller exe.
-//
-// `npm install -g uniner-cli` registers this file as the global `uniner-cli`
-// command (because of the `bin` entry in package.json). We just spawn the real
-// binary with the same argv/stdio and exit with its status code.
-
-'use strict';
-
-const { spawnSync } = require('child_process');
-const fs = require('fs');
-const { realBinaryPath, isInstalled, pkg } = require('../lib/paths');
-
-const exe = realBinaryPath();
-
-if (!isInstalled()) {
-    console.error('');
-    console.error(`[uniner-cli] Real binary not found at: ${exe}`);
-    console.error('[uniner-cli] The npm postinstall step must not have completed.');
-    console.error('[uniner-cli] Try one of:');
-    console.error('[uniner-cli]   npm rebuild -g uniner-cli');
-    console.error('[uniner-cli]   npm uninstall -g uniner-cli && npm install -g uniner-cli');
-    console.error('');
-    process.exit(127);
-}
-
-// stdio:'inherit' forwards stdin/stdout/stderr unchanged so interactive prompts
-// and ANSI color survive. shell:false avoids any path-quoting surprises.
-const result = spawnSync(exe, process.argv.slice(2), {
-    stdio: 'inherit',
-    shell: false,
-    windowsHide: false,
-});
-
-if (result.error) {
-    console.error(`[uniner-cli] Failed to launch ${exe}: ${result.error.message}`);
-    process.exit(1);
-}
-
-// `status` is null when the child was killed by a signal; in that case let
-// the user see we did not exit cleanly.
-process.exit(result.status === null ? 1 : result.status);
+#!/usr/bin/env node
+// Tiny launcher: forward every CLI invocation to the real PyInstaller exe.
+//
+// `npm install -g uniner-cli` registers this file as the global `uniner-cli`
+// command (because of the `bin` entry in package.json). We just spawn the real
+// binary with the same argv/stdio and exit with its status code.
+
+'use strict';
+
+const { spawnSync } = require('child_process');
+const fs = require('fs');
+const { realBinaryPath, isInstalled, pkg } = require('../lib/paths');
+
+const exe = realBinaryPath();
+
+if (!isInstalled()) {
+    console.error('');
+    console.error(`[uniner-cli] Real binary not found at: ${exe}`);
+    console.error('[uniner-cli] The npm postinstall step must not have completed.');
+    console.error('[uniner-cli] Try one of:');
+    console.error('[uniner-cli]   npm rebuild -g uniner-cli');
+    console.error('[uniner-cli]   npm uninstall -g uniner-cli && npm install -g uniner-cli');
+    console.error('');
+    process.exit(127);
+}
+
+// stdio:'inherit' forwards stdin/stdout/stderr unchanged so interactive prompts
+// and ANSI color survive. shell:false avoids any path-quoting surprises.
+const result = spawnSync(exe, process.argv.slice(2), {
+    stdio: 'inherit',
+    shell: false,
+    windowsHide: false,
+});
+
+if (result.error) {
+    console.error(`[uniner-cli] Failed to launch ${exe}: ${result.error.message}`);
+    process.exit(1);
+}
+
+// `status` is null when the child was killed by a signal; in that case let
+// the user see we did not exit cleanly.
+process.exit(result.status === null ? 1 : result.status);