Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
kamen69172yAt one point there was an alternative to npm that tried to remedy just that - installing duplicating packages in a central place, then symlinking them to each project accordingly. I think this was pnpm. I haven't checked it out recently, but it might be worth a shot.
-
j0n4s53102y@kamen you could just install them globally and then you don't have to symlink anything lol
-
kamen69172y@jonas-w This would only work for binaries that you'd expect to call with npx for example. In all other cases things will blow up when you try to build the project.
-
kamen69172y@Jifuna Fucked in what way? Something that's not fixable by rolling back a few commits and/or redoing a build?
-
Jifuna37302y@kamen Not exactly sure but the syslinks didn't work well I suppose because it wouldn't build and told me it couldn't find packages
-
Jifuna37302y@kamen i did :(, but it was like 2 years ago so maybe it has improved. For now I'm fine with just using npm :P
-
Kill them. Kill them all.
cd ~ && find . -name 'node_modules' -type d -prune -exec rm -rf '{}' +
Related Rants
I currently have 5168 node_modules folders on my computer.
Not 5168 folders inside node_modules, but 5168 actual node_modules folders.
That's all. That's the rant.
rant
node_modules
npm
js
javascript