Currently, the latest version of Ramda available on deno.land is 0.27.2, which was pushed around 3 years ago. From what I can gather, ramda on deno.land is actually a mirror of a repo by the apparently abandoned functional.land project, and as a result deno.land/x/ramda refers to functionalland/ramda as upstream instead of here.
Is there any hope of either:
a) The deno.land releases being somehow fixed to refer back to this repository? (Admittedly, I don't know what deno.land/x's policy even is for something like this)
b) A new module name being claimed on deno.land referring to this repo (i.e. deno.land/x/ramdajs)
c) The README fixing the deno.land imports to refer to more recent versions, since Deno is able to import from arbitrary URLs - i.e. just use jsdelivr's GitHub functionality
?
Currently, the latest version of Ramda available on deno.land is 0.27.2, which was pushed around 3 years ago. From what I can gather, ramda on deno.land is actually a mirror of a repo by the apparently abandoned functional.land project, and as a result deno.land/x/ramda refers to functionalland/ramda as upstream instead of here.
Is there any hope of either:
a) The deno.land releases being somehow fixed to refer back to this repository? (Admittedly, I don't know what deno.land/x's policy even is for something like this)
b) A new module name being claimed on deno.land referring to this repo (i.e. deno.land/x/ramdajs)
c) The README fixing the deno.land imports to refer to more recent versions, since Deno is able to import from arbitrary URLs - i.e. just use jsdelivr's GitHub functionality
?