We tried switching to `pnpm` in an internal production repository, and it cut down CI install times by ~70% (140s ➡ 45s, no cache). Also caught a bunch of ghost and duplicate dependencies.
Switching to PNPM might be easier than Yarn PNP for existing projects.
pnpm 6 is out!
It has a better node_modules structure that keeps a cache of modules. So installations make less file system operations in most scenarios.
Also, the lockfile format is updated to reduce merge conflicts and improve readability.
All changes
github.com/pnpm/pnpm/release…
pnpm v6.0.0-rc.1 it out!
Most likely v6.0.0 will be released in a few days.
You may start using v6 already as all breaking changes were already implemented.
github.com/pnpm/pnpm/release…
Have you checked out @pnpmjs ? I don't know if that's the kind of UI you were hoping for, but I thinks its better than npm in that it makes it a lot clearer what is happening and what changes have been made to your computer.
The repo with my website in it is a monorepo so I can more easily manage example code.
I started using PNPM to manage dependencies, but getting that to work with Netlify was a little tricky. Here's how I was able to do it.
seancdavis.com/blog/use-pnpm…
The pnpm docs may now be translated into any language using Crowdin:
crowdin.com/project/pnpm
We know that some of our users don't speak English, so it was crucial to at least have the possibility to localize the website.
Things we know about pnpm v6:
It will drop Node.js 10 support
It will change a bit the lockfile formatting but in a backward compatible way
The node_modules/.pnpm layout will change (to reduce nesting)
Most probably there will be no breaking changes to the global store.
First pnpm v6 alpha version is out.
You can install it through:
pnpm add --global pnpm@dev
In this version the node_modules layout is a bit changed to allow keeping cache of removed packages in node_modules/.pnpm. This increases installation speed in some cases.