Repository navigation
v1.1.3
Fixes
v1.1.2 fixed the original npx-cache resolution bug but introduced a more severe one: npm install --prefix "$install_dir" still reads and parses the consumer's existing package.json, not just the packages named on the command line. Any pnpm (or Yarn) workspace-protocol dependency string there — workspace:*, pnpm's catalog: — crashed the install outright, regardless of --no-save. Caught in the very first real-world CI run against v1.1.2, against verbatra's own docs site, whose apps/docs/package.json uses exactly this.
- Installs into an isolated scratch directory (no
package.jsonto conflict with), then merges the result intoworking-directory— the consumer's own dependency manifest is never read by npm at all. - Fixes a
node_modules/.binsymlink-dereferencing issue found while diagnosing the above (only matters for the merge step, not user-visible on its own). - Adds a
pnpm-workspace-protocolsregression fixture reproducing the exact failure, plus bumps all self-test fixtures to0.9.0(previously0.8.0, stale).
No input or output changes; this is a drop-in upgrade.