When "Everything" Becomes Too Much: The npm Package Chaos of 2024 - eviltoast
  • jeffhykin@lemm.ee
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    9 months ago

    Ryan Dhal, the creator of node, litterally saw the npm problem(s) before incidents like this happened, and created Deno to fix his mistakes. And fix them he did! The Deno import system is incredible. Its basically the only reason I use deno. You can just import URLs directly, the deno vendors (aka caches) them. Deno has an equivlent to npm.org (Deno.land/x) but anyone can import straight from github, or make their npm.org equivlent, or import from their own private server. So if a company wants reliability, they can mirror deno.land while also avoiding unpublishing.

    • QuazarOmega@lemy.lol
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      Yes, that’s really nice! Even though I haven’t touched it in a long time, I remember messing around with it out as soon as it came out a few years ago. There’s also nest.land between the alternative repositories, I find their concept interesting