Summary

Every publish logged:

npm warn publish npm auto-corrected some errors in your package.json when publishing.
npm warn publish errors corrected:
npm warn publish "bin[moshcode]" script name bin/moshcode.mjs was invalid and removed
npm warn publish "bin[moshscript]" script name bin/moshscript.mjs was invalid and removed

"invalid and removed" reads as though the CLI shipped without its entry points. It didn't. npm rewrites ./bin/moshcode.mjs to bin/moshcode.mjs and publishes that — 0.24.0, 0.24.2 and 0.24.3 all have working bins, verified against the registry:

$ npm view moshcode@0.24.3 bin
{ "moshcode": "bin/moshcode.mjs", "moshscript": "bin/moshscript.mjs" }

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 — I let it make the change rather than guessing at the cause from the wording.

Verification

• npm publish --dry-run is now warning-free
• packed the tarball and installed it into a throwaway prefix: both moshcode and moshscript are created and execute (moshcode --version → 0.24.3)
• resulting bin values are identical to what 0.24.3 already has on the registry, so the published manifest does not change
• nothing reads package.json's bin field — the ../bin/moshcode.mjs references in src/ and test/ are relative-URL resolutions, unrelated
• full suite: 1087 passed, 0 failed

No version bump

The published manifest would be byte-identical to 0.24.3's, so there is nothing to release. This rides with the next real release.

🤖 Generated with Claude Code