@dudko.dev/vectorize-cli 0.4.1 → 0.4.2

package/dist/cli.js

@@ -1,6 +1,8 @@
 #!/usr/bin/env node
+import { realpathSync } from 'node:fs';
 import { readFile, writeFile } from 'node:fs/promises';
 import { basename, extname } from 'node:path';
+import { fileURLToPath } from 'node:url';
 import { parseArgs } from 'node:util';
 import { toDxf, toEps, toPdf, traceEncoded, withSize } from '@dudko.dev/vectorize-core';
 const FORMATS = ['svg', 'eps', 'pdf', 'dxf'];
@@ -179,7 +181,24 @@ export async function main(argv) {
     return 0;
 }
 // Run when executed directly (not when imported by tests).
-if (process.argv[1] && import.meta.url === new URL(`file://${process.argv[1]}`).href) {
+//
+// argv[1] is the path the user invoked. For an installed CLI that is the
+// node_modules/.bin symlink npm creates, while import.meta.url is always the
+// real file — so comparing the two without resolving the link makes this
+// condition false exactly when someone runs `vectorize`, and the command exits
+// 0 having done nothing. That is how 0.4.1 shipped. Resolve both to real paths.
+//
+// fileURLToPath rather than building a file:// URL by hand, which mangles any
+// path containing a space or a character URLs escape.
+const invokedPath = (() => {
+    try {
+        return process.argv[1] ? realpathSync(process.argv[1]) : '';
+    }
+    catch {
+        return '';
+    }
+})();
+if (invokedPath && invokedPath === realpathSync(fileURLToPath(import.meta.url))) {
     main(process.argv.slice(2)).then((code) => process.exit(code), (err) => {
         process.stderr.write(`error: ${err instanceof Error ? err.message : String(err)}\n`);
         process.exit(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dudko.dev/vectorize-cli",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "Command-line raster → SVG converter",
   "type": "module",
   "license": "PolyForm-Noncommercial-1.0.0",