News for hackers. Stuff that matters.
Re:Time for developers to address the chaos of Node.js and NPM by gr__or on Saturday March 31, 2018 @01:14PM (#16724127)
True, that WAS a deficiency, though one that seems to be fixed now.

Given that dependencies are also resolved by name in the Ruby & Python I'd think there's no technical reason for why a similar thing wouldn't happen, is there?

Re:Time for developers to address the chaos of Node.js and NPM by krapp on Saturday March 31, 2018 @07:49PM (#16725810)
>Given that dependencies are also resolved by name in the Ruby & Python I'd think there's no technical reason for why a similar thing wouldn't happen, is there?

I don't know, I'm not familiar enough with those languages, but I would guess that if anything similar did happen, it would probably wind up posted here, although absence of evidence isn't evidence of absence.

It may also depend on implementation features besides package names - the worst that should happen if a remote dependency no longer exists is that future updates fail, but a local copy should always exist and the current build should still keep working. To me, vendoring dependencies should be the default.