pnpm workspace: phantom dependency risk when using hoist-pattern
In a pnpm workspace, the hoist-pattern option can be used to lift specific packages into the root node_modules . While this may accommodate legacy tooling that expects a global installation, it also bypasses pnpm’s strict peer‑dependency validation. The result is a phantom dependency that exists only because it was hoisted, not because a consumer explicitly
pnpm