3 ms·
> I think that's true, and true in just about every language/environment Agreed, although it seems as if nodejs may have solved most of the hard problems in th
by twerquie 13y ago
> I think that's true, and true in just about every language/environment
Agreed, although it seems as if nodejs may have solved most of the hard problems in this area by way of their unique require() module loader and the design of npm. After learning it, I wish every package manager worked that way.
- mmgutz 13y agoRan into same issues with nodejs. If one of your dependencies use libxy 1.2 and your app depends on libxy 1.4, you have to be careful which one gets loaded first and hope one is compatiblew with the ohter. Good luck if the APIs are different. NPM seems to solve the problem but it really doesn't.
- daleharvey 13y agoThat is not how node / npm works, it specifically solves this problem, each module gets its own version of its dependancies
- nadaviv 13y agoThis shouldn't be an issue at all. Your app would get libxy 1.4, and your dependency would get libxy 1.2. It shouldn't matter which is loaded first, and unless those modules somehow store something globally, they shouldn't conflict in any way. npm does solve the "multiple versions of a library are used by different packages", unless that libxy you were using did something fishy. Can you give more details?
- rubiquity 13y agoI agree about npm. Having the individual node_modules fixes a lot of dependency management issues. That said, I'm not a fan of Nodd but if I could steal two things from them it would npm and Isaac.