plover-pnpm-workspace

pnpm -F matches by package name, not directory name. In this repo the app/ package is named plover, so -F app matches nothing. Use the path-based filter pnpm --filter ./app <script> instead.

Add the explicit run keyword: pnpm --filter ./app run test:coverage. pnpm treats script names containing colons as a special dispatch case that does not work through the plain --filter shortcut.

With pnpm workspace filters, a trailing -- does not reliably forward flags; vitest receives --coverage as a positional argument. Define a dedicated test:coverage script that calls vitest run --coverage directly.

pnpm 10+ blocks postinstall scripts unless packages are allowlisted in pnpm.onlyBuiltDependencies in the root package.json. Add entries like electron and esbuild there so their native binaries get built.

The corepack pnpm shim ignores .npmrc and fetches the pinned version from registry.npmjs.org, which times out on restricted networks. Prepend the global pnpm directory (~/Library/pnpm) to PATH so the real binary runs instead.

A stray older pnpm (for example Homebrew's) earlier on PATH uses a different store format than the one node_modules was linked against. Put the correct global pnpm first on PATH and verify with pnpm --version.