• UnculturedSwine@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    I’m curious if you mean this one issue talked about in the article is the only reason why node packaging is “fucked” or do you have any citations you can provide that point out other issues with it?

    I feel this is just a natural progression of how the developers wanted it to function and this is an opportunity to resolve it.

    Better that this is done by mistake and resolved than it being used in a malicious attack.

    • dependencyinjection@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      9 months ago

      It’s the cascading nature of the dependencies. You could install a single package that might directly or indirectly depend on 100’s of other packages, which can introduce bugs into existing code bases which can be difficult to fix as you have no control over another library or dependency.