Just got @plone#Volto running on #pnpm, out of #yarn v1. No more missing dependencies, no more strange hoisting issues, no more waste disk space in node_modules. PR 2557
After a frustrating and ultimately unsuccessful attempt at migrating the React Preview monorepo from Yarn v1 to Yarn v3, I tried out PNPM for the first time today.
PNPM worked right away and GitHub Actions now run twice as fast. Nice!
PNPM will now be my go-to 🚀
We had a struggle to release v6.11 but now its latest.
The biggest change is our own implementation of "pnpm pack". Previously we used "npm pack" under the hood
We use pnpm and Microsoft Rush monorepo tooling a lot at some big projects in Adobe. Highly recommended, the flexibility to massage the npm ecosystem both tools provide is invaluable.
Chez Yousign, nous cherchons en permanence à challenger nos outils pour nous améliorer ! 🚀
Comme beaucoup, nous utilisons #yarn comme package manager sur notre stack front. Mais alors pourquoi le changer pour @pnpmjs ? 🐙
Explications 👇 #FrontEndbit.ly/3yR2u9E
Do you have a dependency that only runs on the newest Node.js version? There is a workaround with pnpm to always run it with the needed Node.js version:
{
"test": "pnpm --config.use-node-version=16.4.0 exec jest"
}