3 ms·
You can't do a package cache, because nasal demons erupt whenever you use a package that's not precisely equal and all packages use their own copies of all thei
by GauntletWizard 4y ago
You can't do a package cache, because nasal demons erupt whenever you use a package that's not precisely equal and all packages use their own copies of all their dependencies.
Sane package managers don't try to solve for this problem; they make it clear when you're using bad software.
- weaksauce 4y agoBundler does this just fine. installs every single exact dependency in a central location and then sets the relevant paths to them before running ruby. It works very well. some of the people behind bundler wrote the much loved package manager for rust. I'm not sure where you are getting the thought that other systems haven't done it better.
- GauntletWizard 4y agoThat's exactly the behavior that makes NodeJS unsuitable as a package manager. Some resources are, in fact, globals. You should have a consistent enough API to use those through code that is imported and singular, rather than through importing a dozen versions of the API for each dependency you have.