Hey, you all 👋 after doing some experimentation, I wanted to ask the team (cc @nodejs/website) what you think about adopting pnpm as the package manager for this repository.
Some of the key caveats/benefits I've noticed:
- Installing packages on CI reduced 60% from (varying 20-50seconds to blazingly 4-7 seconds)
- Running package binaries do not require
npx
- Native monorepo support if we ever need
- Smaller
node_modules and cache footprint (making the GitHub Actions cache storage have more space) (Around 70% less footprint)
Some of the disadvantages:
- Requires Extra Step on CI to install PNPM or use
Corepack
- Not natively installed with Node.js, so newcomers need also to install
pnpm
I also want the opinion of the @nodejs/build team and the TSC @nodejs/tsc as I want to ensure that this change is not controversial nor conflicting with any of our bylaws and/or creates an adverse affect on the "npm" package manager (as if this repository does any endorsement to pnpm over npm which is not the case).
Hey, you all 👋 after doing some experimentation, I wanted to ask the team (cc @nodejs/website) what you think about adopting
pnpmas the package manager for this repository.Some of the key caveats/benefits I've noticed:
npxnode_modulesand cache footprint (making the GitHub Actions cache storage have more space) (Around 70% less footprint)Some of the disadvantages:
CorepackpnpmI also want the opinion of the @nodejs/build team and the TSC @nodejs/tsc as I want to ensure that this change is not controversial nor conflicting with any of our bylaws and/or creates an adverse affect on the "npm" package manager (as if this repository does any endorsement to
pnpmovernpmwhich is not the case).