I wanted to ask whether you’d be open to discussing pnpm for this repo instead of npm.
I tried the switch locally and it felt like a fairly good fit for this project, mainly because of the repo’s mix of Tauri, Svelte, Playwright, Rust-side workflows, and worktree-heavy development.
A few things stood out:
-
It surfaced an undeclared direct dependency
During the migration, pnpm exposed that @codemirror/language was being imported directly but was not explicitly listed in package.json.
npm still worked because of hoisting, but pnpm made that issue visible right away.
-
It may fit the worktree workflow better
Since this repo often uses separate git worktrees, pnpm’s shared store / linked dependency model seems potentially helpful.
My impression is that this could reduce duplicated node_modules footprint when several worktrees exist at once, compared with reinstalling a more fully materialized dependency tree in each worktree.
If you’re open to it, I’d be happy to put together a small PR.
I wanted to ask whether you’d be open to discussing
pnpmfor this repo instead ofnpm.I tried the switch locally and it felt like a fairly good fit for this project, mainly because of the repo’s mix of Tauri, Svelte, Playwright, Rust-side workflows, and worktree-heavy development.
A few things stood out:
It surfaced an undeclared direct dependency
During the migration,
pnpmexposed that@codemirror/languagewas being imported directly but was not explicitly listed inpackage.json.npmstill worked because of hoisting, butpnpmmade that issue visible right away.It may fit the worktree workflow better
Since this repo often uses separate git worktrees,
pnpm’s shared store / linked dependency model seems potentially helpful.My impression is that this could reduce duplicated
node_modulesfootprint when several worktrees exist at once, compared with reinstalling a more fully materialized dependency tree in each worktree.If you’re open to it, I’d be happy to put together a small PR.