Deno uses https typically... I like the change myself... hoping this leads to better compatability with deno... or at least with deno, maybe importing `npm+node:...` since it's node-style modules from npm. And have deno auto-include the node compatibility shims.
That said, deno has become much more of a goto for me the past few months alone... there's only a handful of things I haven't found implemented that I need... it's been a nicer experience for orchestration scripting.