Version list is not understandable and missleading

[KnisterPeter]

Describe the bug

I think the version list on this package (example) https://npmx.dev/package/node is not very helpful. It shows the latest (fine) and then version which are released long long ago. While hiding the more useful versions released more recently in Other version.

Additional context

Not sure if this is specific to the node package.

Logs

[t128n]

One possible UX solution that wouldn't break the experience for well-tagged packages like Next or Vite could be a toggle in the version preview to switch between the tags view (current behavior) and a recent releases view, where versions are sorted by release date descending regardless of tagging. That would be more useful for packages like node, with inconsistent tagging practices

[KnisterPeter]

For vite I also don't see why 6.0.0-alpha.24 released around sep 24 is more important than 7.3.2 released around apr 26. Not sure how well-tagged this is.

[t128n]

6.0.0-alpha.24 is the "current" alpha head whereas 7.3.2 is just one of many latest-channel releases, with newer ones have already replaced it. Since the UI can show only a limited number of versions across all packages, prioritizing channel heads makes sense imo