Some notes when I migrate pnpm inside my team @acao

Why use pnpm

performance: it's the fastest package manager out there, yarn the catfish went in a completely different direction after 2 (platforming, including advanced features like the plugin system)
monorepo support: filter is by far the best filter in the package manager, probably not one of them (lerna/yarn2/nx don't work as well)
disk utilization: due to the use of hard links, it is like maven the same package only occupies a space, if you have 100 projects, node_modules will not be copied 100 copies
Avoiding phantom dependencies: solves the common problem of using dependencies without declaring them, e.g. two modules depend on different versions of lodash, and there is no certainty which version of lodash is used, which can cause very strange errors

Actual performance comparison

pnpm migration guide

rm package-lock.json
npm i -g pnpm
cd matrix/
pnpm i/rm
pnpm dev/build
# Run the specified command on all modules
pnpm --filter . run initialize

Limitations

Does not provide sophisticated monorepo tools
Does not support some npm modules (but much better than pnp, at least vue is officially using pnpm, so it's impossible to be incompatible)

Move to yarn 3 + pnp, pnpm or latest npm? #2185