ryenus
ryenus
Hmm, even if the content of https://nodejs.org/dist/index.tab is also somehow a function of time?
TBH I don't see why we cannot put it behind a flag such as `--supported`, meanwhile maintain the existing behaviour as default?
> for a project's preferred node version to change based on the passage of time Hmm, here the request is only about **`nvm ls-remote`**, with no involvement with `nvm use`...
> That affects `nvm install` as well, though. Maybe not if it's an option only for `nvm ls-remote`? I guess this request would be more appealing back when `nvm_print_versions` was...
> Is your motivation to hasten/shorten the response of nvm ls-remote? Well yes, that's it. BTW, and which *OP*? I guess I'm a bit confused.
Ahh, I was actually thinking the same, maybe my *OP* should have been more concise :-)
> Would a `--min=18`, for example, suffice here? Yes, that also works! And it has the advantage of being more flexible. Maybe we can even have it as the default?...
> add an env var that sets that value, so it's easy to set your own default? That would be really great! Much appreciated 👍
For example, running `NVM_MIN_VER=18 nvm ls-remote --lts` when v14 and v16 are installed:
Performance-wise there's not really much change or overhead, you can trust that awk is fast :-) Sometimes it might even run faster, esp. when many older versions are skipped. Meanwhile...