Strict symlink isolation versus selective hoisting for legacy tool compatibility in pnpm workspaces
A pnpm workspace stores packages once in a content-addressable store and creates per-project node_modules via symlinks. Strict isolation preserves deterministic resolution and disk efficiency, but changes resolution paths compared to a flat layout. Selective hoisting via public hoist patterns and node linker options can expose specific packages at the worksp
pnpm