Clojurians Log v2

https://nodejs.org/api/esm.html#node-imports

how it connects to deno: deno requires you to load built-in modules like this, if you want code to work both in deno and node.js (which I'm doing in nbb for example, and this works with shadow-cljs, not with vanilla CLJS)

this looks like a hardcoded special case or do you have documentation stating otherwise?

how is this special cases?

node: URLs are supported as an alternative means to load Node.js builtin modules.

meaning node is a magic url, this isn't going to work for some random library

"node:" is a specific url to target built-in libraries and deno supports it too. what do you mean with "random library"?

I mean this is not a real url protocol, it's just some ad-hoc thing in Node.js

yes. CLJS supports Node.js right?

we're not talking about CLJS, I just have no idea about this and just collecting information

ok. yes, it's a magic url that node invented so make it easier to recognize that you're targeting a built-in. let me see if I can find more docs about it

here's the Deno side of things. https://docs.deno.com/runtime/fundamentals/node/ Deno mimics Node modules in their runtime when you load them with node:...

so it's kind of ad-hoc but it is required if you want to write code that runs in both Node.js and Deno

god slop in that documentation

JavaScript the trashfire that never keeps giving

why do you think it's slop, because of the ;?

anyways - ok - I think the problem is at the node indexing level, we probably try to resolve this is as a real module

As of Deno 2.8, over 75% of Node's own test suite passes in Deno, covering nearly every node: module. Most pure-JavaScript npm packages work without changes. The honest caveats: some APIs are partial, packages with native addons need a local node_modules directory, and a few tools assume npm's exact on-disk layout. The sections below cover each of those cases.

"The honest caveats:" ... what???

haha oh yes

https://clojure.atlassian.net/browse/CLJS-3482