When "Everything" Becomes Too Much: The npm Package Chaos of 2024 - eviltoast
  • labsin@sh.itjust.works
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    9 months ago

    Other package managers, like nuget, throw errors if all dependencies on a package cannot be met by a single version.

    This is probably the result of it copying all libraries in the same output directory and that .net cannot load 2 different versions of the same library so more an application restriction.

    The downside of this is that packages often can’t use newer features if they want to not block the users of that library and that utility libraries have to have his backwards compatibility so applications can use the latest version while dependent libraries target an older version. Often applications keep using older versions with known security issues.