From 7171553150a1e6ac9fb6319e636f8bac6f9dc497 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Thu, 6 Aug 2026 09:20:43 +0000 Subject: [PATCH] fix(pkg): drop the ./ prefix npm strips from bin paths anyway MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Every publish logged: npm warn publish npm auto-corrected some errors in your package.json npm warn publish "bin[moshcode]" script name bin/moshcode.mjs was invalid and removed which reads as though the CLI shipped without its entry points. It did not: npm rewrites `./bin/moshcode.mjs` to `bin/moshcode.mjs` and publishes that, so 0.24.0, 0.24.2 and 0.24.3 all have working bins — checked against the registry. So this changes nothing for anyone installing moshcode. It writes down what npm was already doing, and removes a warning that would cost the next person the same few minutes to dismiss. `npm pkg fix` produces exactly this diff and nothing else. No version bump: the published manifest is byte-identical to what 0.24.3 already has, so there is nothing to release. It rides with the next one. Co-Authored-By: Claude Opus 5 (1M context) --- package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package.json b/package.json index 3342692..3d2b35c 100644 --- a/package.json +++ b/package.json @@ -12,8 +12,8 @@ "url": "https://github.com/moshcoder/moshcode/issues" }, "bin": { - "moshcode": "./bin/moshcode.mjs", - "moshscript": "./bin/moshscript.mjs" + "moshcode": "bin/moshcode.mjs", + "moshscript": "bin/moshscript.mjs" }, "scripts": { "start": "node bin/moshcode.mjs",