You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Better Monorepo Tooling: Native recursive commands and filtering (--filter, -r) make working in multi-package repos much smoother.
CI & Dev Experience: Faster cold installs with pnpm fetch, deterministic lockfile, and smooth integration with tools like Turborepo for caching and parallel builds.
dependsOn: enforces the pipeline (e.g., compile -> generate-types -> build), so nextjs can’t build on stale typechain types
Explicit inputs/outputs: only affected tasks rerun -> unchanged packages skip rebuilds while artifacts like .next/**, typechain-types/** are reused
First-class long-running tasks: persistent: true for dev/chain/fork orchestrates local Hardhat + Next (I had previously been using a vs code tasks.json to do similar, but turborepo is definitely better and more modern solution)
Next Steps
Please let me know if there is any interest and if this would even be considered. If so, I'm happy to create a PR on the latest code to demonstrate what the migration would look like.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Has there been any discussion to migrate from yarn workspaces to pnpm?
I personally modified my latest scaffold-eth project to
pnpm+turborepoand I find the dev experience to be much better.Arguments for pnpm over yarn:
pnpminstalls are significantly faster (global content-addressable store)pnpmhard-links dependencies, reducing node_modules size when you have lots of projects.pnpmenforces correct dependency declarations--filter,-r) make working in multi-package repos much smoother.pnpm fetch, deterministic lockfile, and smooth integration with tools like Turborepo for caching and parallel builds.Benefit of turborepo caching:
dependsOn: enforces the pipeline (e.g., compile -> generate-types -> build), so nextjs can’t build on stale typechain types.next/**,typechain-types/**are reusedpersistent: truefor dev/chain/fork orchestrates local Hardhat + Next (I had previously been using a vs code tasks.json to do similar, but turborepo is definitely better and more modern solution)Next Steps
Please let me know if there is any interest and if this would even be considered. If so, I'm happy to create a PR on the latest code to demonstrate what the migration would look like.
Beta Was this translation helpful? Give feedback.
All reactions