fix(pkg): drop the ./ prefix npm strips from bin paths anyway - #313
Merged
Conversation
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) <noreply@anthropic.com>
ThreatCrush Security Scan92 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 42
…and 42 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Every publish logged:
"invalid and removed" reads as though the CLI shipped without its entry points. It didn't. npm rewrites
./bin/moshcode.mjstobin/moshcode.mjsand publishes that — 0.24.0, 0.24.2 and 0.24.3 all have working bins, verified 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 fixproduces 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-runis now warning-freemoshcodeandmoshscriptare created and execute (moshcode --version→ 0.24.3)binvalues are identical to what 0.24.3 already has on the registry, so the published manifest does not changepackage.json'sbinfield — the../bin/moshcode.mjsreferences insrc/andtest/are relative-URL resolutions, unrelatedNo 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