Why does 'ls-remote' start from the bottom of versions and not the top?

[raphaellueckl]

[Sorry for removing the issue template, but none of the points made sense for this ticket.]

I always wonder why 'ls-remote' doesn't start from the newest version, which mostly would allow for almost instant CTRL+C without waiting half a minute for the complete list. Is there any particular reason for this? Usually I am always too little bothered to mention it somewhere but today I thought that this has been the case for several years now and it finally should be discussed. :)

Seriously, who wants to install the node versions below 1? Below 10? Below 15?.... That ordering should be descending in my humble opinion.

Thanks for this awesome product! 🚀

[ljharb]

Because that’s how they’re listed on the remote server, so it would be a lot slower to reverse the entire download - you’d end up waiting more time.

[ljharb]

i mean you can just list the latest major, or --lts, etc, so usually that’s what i do when I’m not trying to see everything.

[raphaellueckl]

@ljharb Thx for responding. If it's the remote that delivers the list in a badly sorted way, can we somehow raise a ticket there? Wherever that is.

[ljharb]

You certainly could file an issue on nodejs/release requesting the order be inverted - although that would probably break lots of version manager users, so it’s only really practical as a separate index file, which probably won’t be worth it since it’d be two sources of truth.

[raphaellueckl]

😢😭😭

[kuchta]

@raphaellueckl I'm actually quite glad that it is this way, since on my machine the listing is instant and I don't have to scroll some 18 pages to get to the latest versions. But if you really prefer it in reverse order nvs seems to have it that way.