@versions to list down all versions of a module [Enhancement]

any version management service requires being able to discover all the available versions,

lets say in a module, I use

import something from "https://deno.land/x/something@1.2.0/main.ts"

it’d be nice if I could do something similar to

curl https://deno.land/x/something@versions

if it’d return

{"versions": ["0.0.1", "1.0.0", "1.0.1", "1.1.0", "1.2.0", "2.0", "2.1"]}

there’s currently no standardised way of discovering all available versions of a file,

currently, for example, deno-udd, uses a variety of techniques to find all available versions, including

• checking github releases
• web scraping

apart from the other issues in this (like github’s rate limiting), there is no standard, meaning that every person who hosts a file on their site will have to tell deno-udd to be able to support their website, and every other deno version management service like deno-udd to be able to support their website, and like, what may be a standard way in one version management service might not be supported in another

I like the @versions method cause is simple, and probably super easy to implement

further, it’d be even better if it could support additional parameters like

{
    "versions": ["0.0.1", "1.0.0", "1.0.1", "1.1.0", "2.0", "2.6.9"],
    "deprecated": ["1.*"],
    "fatal-risk-of-use": ["<1.0.0"],
    "dog-person-wrote-code": false,
    "cat-person-wrote-code": true
}

relevant issue https://github.com/hayd/deno-udd/issues/10

[kidonng]

Why bother about GitHub’s rate limit when we have CDN like jsDelivr?

https://data.jsdelivr.com/v1/package/gh/denoland/deno

This is pretty simple to implement.

[lucacasonato]

deno.land also only works for github repos

@therealadityashankar That is not correct. It can also proxy any URL or packages from NPM.

There might be a solution for the rate limit. I will look into this further.