chore: rename npm package to rig-constellation#14
Merged
Conversation
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 npm name
rigis already taken (an unrelated package: "barepipe platform for node webapps", v0.7.0), sobunx rigruns that, not ours — and we can't publish underrig.Renames the package to
rig-constellation(matches the product metaphor). The installed command staysrig(bin name unchanged). Install becomesbunx rig-constellation/npm i -g rig-constellation.package.jsonname →rig-constellationbunx rig→bunx rig-constellation, global-install line updatedbun install --frozen-lockfilestill passes (lockfile unaffected)Note: README also edited on the demo-video branch — minor merge reconciliation may be needed depending on merge order.
🤖 Generated with Claude Code