Installation and availability
pnport 0.1.0 has not been released. The current source does not provide a published npm package, native archive, POSIX or PowerShell installer, or Homebrew formula. Do not use an unpublished package version, guessed download URL, or source-only launcher as an installation method.
Planned distribution
A complete release is planned to provide prebuilt GitHub archives with checksums and signed verification material, direct installers for POSIX and PowerShell, prebuilt Homebrew packages, and the @delino/pnport npm launcher. The npm launcher will require Node.js 22 or newer and the matching native optional package. The standalone native CLI will not need Node.js merely to start.
The release targets are:
Linux support includes static child executables as a release requirement. Musl hosts and mixed-architecture execution are excluded. These are release targets, not a claim of current package availability or verified compatibility. Every target must pass execution and installation validation before 0.1.0 is published; there is no partial preview release.
Before a future install
pnport needs an already installed Yarn 4 Plug'n'Play project with .pnp.cjs. It does not install dependencies, generate a PnP manifest, update a lockfile, or create a physical project node_modules directory. Keep the selected project's Yarn installation intact.
When a verified release is published, choose an explicit version and confirm the installed CLI with pnport --version and pnport doctor. The following examples are for a future published version only; replace <published-version> after checking GitHub Releases or the npm package.
For npm or Yarn 4, keep optional dependencies enabled so the launcher can select the matching native package:
For a direct install on macOS or glibc Linux, download the POSIX installer and pin the version:
On Windows, use the PowerShell installer:
After the first release, supported macOS and glibc Linux hosts can also use brew install delinoio/tap/pnport. Direct installers verify archive checksums and activate the executable with its matching adjacent interception library. Keep those two files together when using a native archive. No method performs an automatic update. Continue with the command reference or see releases and rollback for version policy and verification.