News for hackers. Stuff that matters.

A comment on Deno on MDN. Parent comment

Re:Deno on MDN by lucacasonato on Monday August 23, 2021 @11:31AM (#28277384)
We don't ignore these problems. We find web compatible ways to solve them. If you had done just about 3 seconds of research before posting, you would have noticed we have support for import maps[1]. These elegantly solve the issue in a way that also works in the browser. No node_modules needed :-)

[1]: https://deno.land/[email protected]/linking_to_external_code/im...

[ Parent | on HN ]
Re:Deno on MDN by whateveracct on Monday August 23, 2021 @12:09PM (#28278051)
That looks like the output of a package manager (like a cabal freeze file), but if that's all you got then you don't have a package manager yet.
[ Parent | on HN ]
Re:Deno on MDN by spankalee on Monday August 23, 2021 @11:51AM (#28277714)
Import maps are great if you know all the mappings you want to make.

That requires that you know every way that conceptually the same packages are imported in the entire transitive module graph, which is hard enough on its own, but also requires crawling the whole live module graph to discover all the imports. I don't see how this isn't just npm-but-worse.

[ Parent | on HN ]
Re:Deno on MDN by whateveracct on Monday August 23, 2021 @12:10PM (#28278068)
It'll eventually evolve into npm-but-different once Deno gains more adoption and its users learn they need a real package manager. And the cycle continues.
[ Parent | on HN ]
Re:Deno on MDN by andrew_ on Monday August 23, 2021 @12:17PM (#28278164)
projects like `trex` [1] take the heavy lifting out of the equation, and are nicely compatible with a lockfile. This may feel familiar, even somewhat similar, but after using it for a short time I state with confidence that it's not a package manager. This paradigm is enjoyable.

[1] https://nicedoc.io/crewdevio/Trex

[ Parent | on HN ]