chore: drop vestigial npm packaging#44
Merged
Merged
Conversation
The CLI ships only as a Bun-compiled single binary via the Homebrew tap; it is never published to npm. Keeping a bin/publishConfig let a local 'npm i -g .' install a global 'agent' that shadowed the brew binary and froze at an old version. Mark the package private and remove bin/files/publishConfig so that footgun is gone.
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.
The CLI is distributed only as a Bun-compiled single binary via the Homebrew tap — it is never published to npm (
@ellipsis/cli404s on the registry, and no workflow publishes it).The leftover
bin/files/publishConfigin package.json let a localnpm i -g .install a globalagentthat shadowed the Homebrew binary on PATH and silently froze at an old version. This marks the packageprivateand removes those fields so the footgun is gone.No effect on the release: the version stamp step (
npm version) works on private packages, and distribution is the compiled binary, not npm.Typecheck clean; 224 tests pass.