It depends. If you switch between different branches a lot, Library just grows to infinite sizes due to storing everything from each branch that is unique to those branches. I once had to clear about 600 gigs of library lol.
Not sure, but probably. I only used yarn 1. Never got around to trying yarn 2+ as migrating our fairly large monorepo project at the time felt like a pretty large and complicated ordeal. By the time I switched jobs npm was already a whole lot better in the ways most important to me.
The little I’ve read about and used pnpm so far it seems a lot more plug n play than yarn while bringing big benefits. Even workspaces seems a lot simpler than it ever was with yarn (at least when I used it). Love the idea of non-flat node_modules and simplified lock files as well.
Time will tell if npm incorporates enough of pnpm’s features to make it obsolete eventually but for now I can understand why it seems so widely adopted.
laughs in Cargo
./targetCame here to say this, but I was delayed by having to clean my cargo target folder.
Somewhere to the right has to be unity's Library folder
those devs understand why their assets are so large. but if you ask a js dev why they webpack instead of compiling they just start crying and run away
It depends. If you switch between different branches a lot, Library just grows to infinite sizes due to storing everything from each branch that is unique to those branches. I once had to clear about 600 gigs of library lol.
https://pnpm.io/
That's the one that's like Yarn’s global cache, but without compression, right?
Not sure, but probably. I only used yarn 1. Never got around to trying yarn 2+ as migrating our fairly large monorepo project at the time felt like a pretty large and complicated ordeal. By the time I switched jobs npm was already a whole lot better in the ways most important to me.
The little I’ve read about and used pnpm so far it seems a lot more plug n play than yarn while bringing big benefits. Even workspaces seems a lot simpler than it ever was with yarn (at least when I used it). Love the idea of non-flat node_modules and simplified lock files as well.
Time will tell if npm incorporates enough of pnpm’s features to make it obsolete eventually but for now I can understand why it seems so widely adopted.
I mean, the essential difference of no node_modules is shared, as are workspaces.
I think pnpm is more manual, but therefore less magic than yarn. More compatible, less stuff just works
the only JS package manager I have on my system.
for unruly projects, I just pass --shamefully-hoist
2012 called, they want their meme back
It's still true tho.
Heavy objects cause time dilation.
That's heavy man
Great Scott!
I love when I have to wipe node_modules and reinstall and it takes like an hour because there's thousands of packages lol
antique programming memes roadshow
you know, this meme is old as hell, but I still like it.
I have not laugued at one of these out loud untill now.
i recently begged my cs teacher to install npm on the school computers. shouldnt have been suprised when i immediately ran out of storage
Let me introduce you to my little friend: conda
I would've made this joke earlier but I was waiting for Conda to resolve dependencies
Try micromamba, its a drop in replacement for conda is 100x faster for resolving
Oh yes. Creating an empty environment can easily take up several gigabytes...
i just checked and it seems to be a really cool package manager for several languages. but how does that help with storage limitations?
Oh no, I meant it will bloat your storage more than anything else
oh nice! ill try that on the school computers
npm searchagrees.npm install everything
https://www.bleepingcomputer.com/news/security/everything-blocks-devs-from-removing-their-own-npm-packages/
Nodes baggage just adds weight to the depth of the supply chain risk.
Time to write in C
The overlap between people that write C and people that write JavaScript is negligible.
Words of Wisdom