Skip to content

Follow upstream: npm ships only a launcher that downloads release archives #19

Closed
2 of 2 issues completed

Description

@Pho3niX90

Upstream stopped publishing the CLI executables to npm in pingdotgg/t3code#20148 ("bye npm"). We should follow, once the pending upstream merge is in.

What upstream changed

Before #20148, npm carried a launcher plus five 80–250 MB per-platform packages holding the executables. npm's publish-time scanning held those back for up to an hour after the launcher went live, so installs in that window got a launcher with no executable.

Now only a small launcher goes to npm (scripts/npm-launcher/t3.mjs, built by scripts/build-npm-launcher.ts). On first run it downloads its version's CLI archive from the GitHub Release, checks it against SHA256SUMS, and unpacks it into <T3 home>/runtime/versions/<version>. That is the folder the install scripts and update already use. npx and npm install -g keep working.

We are following this rather than dropping npm entirely: staying on upstream's design keeps merges simple.

To do

  • Merge upstream main through at least #20148 into fork/main. It deletes scripts/build-npm-platform-packages.ts and rewrites much of apps/server/src/cli/invocation.ts.
  • Redo the CLI rename on top of it: the command is par3, with p3 as an alias, and t3 is no longer installed. The rename is written but not yet committed. It edits both of the files above, so those edits move onto upstream's new versions.
  • In the new launcher: package @paritylabs/par3 with bins { par3, p3 }. Change the download base URL and the releases link from pingdotgg/t3code to Pho3niX90/t3code, and change the "downloading T3 Code" text to Par3.
  • Blocker: fork releases only ship the Windows desktop installer. The release workflow has to publish the CLI archives and SHA256SUMS to each release. Without them the npm launcher, the install scripts, par3 update and SSH hosts can't install Par3.
  • npm setup: only @paritylabs/par3 needs a trusted publisher. The @paritylabs/par3-<platform> packages are no longer needed and should never be created.

Activity

  1. Pho3niX90 commented on Oct 22, 2026

    @Pho3niX90
    OwnerAuthor

    Closing: the launcher/release migration is now complete. The release workflow publishes and verifies the platform CLI archives plus SHA256SUMS, and the npm launcher is publishing successfully through the configured trusted publisher (see #32 and #33).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions