Being able to hide versions.

[andreespirela]

Describe the solution you'd like
I would like to open up a discussion and see what you all have to say about a feature that I'm desiring since a while ago. The feature would consist in being able to hide a specific version from the website (nest.land). The usage would be something like eggs hide 1.1.2 and from there on, the version 1.1.2 will stop appearing on the website.

Note: It would still be usable as it is part of the blockchain and it would go against the philosophy of nest.land to make it unavailable. So, if people point out to that specific version (which is hid), they could still use it. But in regards to the website, it would be hidden in the website.

[littledivy]

Why would someone want to hide a specific version from the website but not from the blockchain. 🤔

If they publish a broken package by mistake, they will have to create a new stable version to fix it anyways. The website will show the stable version after it is uploaded so the prev broken version is already hidden to the user (unless they choose to see it).

Instead of not displaying the package, we could add a feature to make a particular stable version "unstable".
Something like eggs report 1.1.2 should do.

[zorbyte]

We should consider allowing people to add a X-Deno-Warning header and proxy the module for modules that require notices such as unstable or insecure.

[andreespirela]

Why would someone want to hide a specific version from the website but not from the blockchain. 🤔

If they publish a broken package by mistake, they will have to create a new stable version to fix it anyways. The website will show the stable version after it is uploaded so the prev broken version is already hidden to the user anyways (unless they choose to see it).

Instead of not displaying the package, we could add a feature to make a particular stable version "unstable".
Something like eggs report 1.1.2 should do.

I think that’s a good point. Unstable versions should do it, something like eggs report would make the version unstable, and so it wouldn’t be shown on the “stable” dropdown, rather there will be another drop down for versions marked as unstable. I guess we would have to think how we will fetch the unstable versions (how we would differentiate the stable & unstable versions when requesting them with the URL)...