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.

that's 5168 too many.

At 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.

@kamen you could just install them globally and then you don't have to symlink anything lol

@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.

@kamen didn't npm shot down that approach for security reasons?

Enjoy web development

@IntrusionCM I don't remember, but it's possible, yes.

@kamen I tried this but it fucked some of my projects sadly

@Jifuna Fucked in what way? Something that's not fixable by rolling back a few commits and/or redoing a build?

@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

@Jifuna Wipe node_modules, do an npm install anew and try again.

@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

Just use deno.

Kill them. Kill them all.

cd ~ && find . -name 'node_modules' -type d -prune -exec rm -rf '{}' +