The idea is to deprecate yarn in favor of pnpm as it offers - better disk space efficiency - speed (compared to yarn) - deterministic installs - stricter dependency isolation
Sounds interesting. It looks like we use the Debian packaged "yarn" atm, but there is no package for "pnpm". Guessing that's part of why we're on yarn 1.x and not yarn 2.x as well...
Also, if it stores the modules somewhere than in ./node_modules, then maybe I wouldn't have to chronically be typing "grep --exclude-dir=node_modules" haha.
Updating Yarn and using the Yarn PnP strategy (default for new projects) doesn't look bad either: https://github.com/pnpm/pnpm?tab=readme-ov-file#benchmark https://yarnpkg.com/features/pnp https://yarnpkg.com/blog/release/4.0#performances Ultimately both are fast and well maintained. So whichever someone motivated to attempt to make it happen finds easier to migrate to or find differentiating features for our daily use. Thanks for opening the topic! :)