mirror of
https://github.com/pnpm/pnpm.git
synced 2026-03-31 05:22:00 -04:00
* fix(exe): create pn/pnpx/pnx binaries in linkExePlatformBinary When pnpm auto-manages its version via the `packageManager` field, it installs @pnpm/exe to the store with scripts disabled. The `linkExePlatformBinary` function replicates setup.js by linking the platform binary, but it only created the `pnpm` binary. The published @pnpm/exe tarball has placeholder files for pn, pnpx, and pnx (written by prepare.js). Without setup.js running, these remain as placeholders, causing "This: not found" when invoked. Create pn (hardlink to native binary) and pnpx/pnx (shell scripts) in linkExePlatformBinary, matching what setup.js does. * fix(exe): remove unnecessary placeholder writes on Windows * test(exe): verify pn/pnpx/pnx are created by linkExePlatformBinary * test(exe): e2e test that setup.js creates all binaries after prepare.js Runs prepare.js (simulating publish) then setup.js (simulating install) and verifies that pnpm and pn are hardlinks to the platform binary, and pnpx and pnx are executable shell scripts. Also fixes setup.js to unlink before writing shell scripts, so that the 0o755 mode is applied even when prepare.js already created the file with 0o644. * fix: use node: protocol for imports * fix(exe): use shell script aliases for pn instead of hardlinks pn, like pnpx and pnx, is now a shell script (`exec pnpm "$@"`) instead of a hardlink to the native binary. This avoids duplicating the ~100MB binary. Updated in both setup.js (registry installs) and linkExePlatformBinary (store installs via version switching). * fix(exe): revert pn back to hardlink, keep pnpx/pnx as shell scripts Hardlinks have zero overhead and no disk cost (shared inode). Shell scripts are only needed for pnpx/pnx which inject the dlx arg. * fix(exe): only ignore ENOENT in createShellScript unlink * fix(exe): publish pnpx/pnx with real content instead of placeholders prepare.js now writes the actual shell scripts for pnpx and pnx (and their .cmd/.ps1 Windows wrappers) instead of placeholder text. This means setup.js and linkExePlatformBinary only need to handle the native binary hardlinks (pnpm, pn) and the Windows bin rewrite. The published tarball contains the correct pnpx/pnx scripts for all platforms, so they work even when lifecycle scripts don't run (e.g. store installs during auto version management). * fix(exe): skip hardlink test when platform binary is unavailable The platform-specific packages (@pnpm/linux-x64 etc.) are optional dependencies only available in the @pnpm/exe package, not in CI test environments. Split the test so prepare.js content verification always runs, while the setup.js hardlink test skips gracefully. * style: use single quotes in test