zkochan on v7
chore(deps): update chore(deps): update chore(release): 6.28.0 and 1 more (compare)
zkochan on v6.28.0
zkochan on main
chore(deps): update chore(release): 6.28.0 (compare)
zkochan on main
chore(deps): update (compare)
dependent: package-namefield on each record which specifies the package which depends on the record's package
optionalDependenciesin each package. So no need in
@/all pnpm version one is released!
if you have 100 projects using lodash
@/all pnpm version 1.3 is out
It is 5% faster than 1.2 and has a nice new summary of added/deleted root dependencies:
all the changes here
[WARN] long wall of text coming up
I didn't know about pnpm until today actually, but it sure sounds great :clap: .
Before I give it a shot in my team, I wonder if you have already solved the following problem: creating a deployable bundle that is space-optimized when unpacked (the archive compressor would take care of most of the duplication, but we have limited disk space when unpacking the bundle).
A bit of context is that today we do something similar to pnpm (i.e. we don't use npm install the regular way, and use symlinks to gain speed) and at build-artifact step, we actually do a full copy and call
npm dedupe <rant>npm@3 actually, since that's the only one that still works properly...</rant>
AFAICS using pnpm, instead of our install setup, should work just as well, and then we could still do a full copy (i.e. no hardlinks) and call
But do you (pnpm users or pnpm itself) have anything to aid the need for a deduped node_modules ? Thanks!