Repository navigation
Publish the npm binaries as versions of @funky-dev/cli - #6
Merged
Merged
Conversation
Instead of six @funky-dev/cli-<platform> packages, each platform's binary is now published as a version of @funky-dev/cli itself (0.1.1-darwin-arm64, …, each on its own platform dist-tag so none becomes latest), and the main version depends on them through npm aliases (@funky-dev/cli-darwin-arm64: npm:@funky-dev/cli@0.1.1-darwin-arm64), the way @openai/codex ships. Installs are unchanged, and there is one package to own, configure trusted publishing for, and show on npm. The already-published check no longer prints npm's 404 for versions that aren't out yet. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
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.
What
Ships the npm binaries the way
@openai/codexdoes: as versions of the one package instead of six separate@funky-dev/cli-<platform>packages.@funky-dev/cli@<version>-<platform>(for example0.1.1-darwin-arm64, withos/cpuset). Each goes on a per-platform dist-tag (darwin-arm64, …), so none of them becomeslatest, and the tag list stays at 6 +latest/nexthowever many releases there are.@funky-dev/cli@<version>lists them as aliased optional dependencies:"@funky-dev/cli-darwin-arm64": "npm:@funky-dev/cli@0.1.1-darwin-arm64". npm installs only the matching one, under the same folder name as before, sobin/funky.jsis unchanged apart from its comment.Why: one package to own, one trusted-publisher setup instead of seven, and one package on npm. Installs work exactly as before.
After this ships (v0.1.1), the six
@funky-dev/cli-*packages that0.1.0uses get deprecated with a pointer to@funky-dev/cli.Testing
Against a local Verdaccio registry, using the real v0.1.0 release binaries:
node npm/publish.mjs(with--provenanceremoved, which only works in CI) publishes the 6 platform versions and then the main one. Dist-tags:latest: 0.1.0plus one per platform. A second run skips all 7 as already published.npm install -g @funky-dev/clion macOS arm64 installscli+cli-darwin-arm64(2 packages), andfunky --versionprints0.1.0.npx @funky-dev/cli --versionworks too.npm install --os/--cpufor linux/x64, linux/arm64, win32/arm64 and darwin/x64 each installs only its own build (0.1.0-<platform>).funky --version.🤖 Generated with Claude Code