williamkapke
LTS description
Just like Nightly, can you also write which node version is the stable, LTS, end-of-support?
Hey- that's a decent idea! 🤔 I'm swamped right now so I'll leave this open as a TODO. Maybe a PR will come in!
It would be nice to have an option to show only maintained versions, too. Nobody should be worrying for something older than Node.js 8.x anyway... :-)
I support down to 0.4; it's a fine checkbox to add, but there are plenty of very good reasons to not leave users stuck on unmaintained node versions in the lurch.
there are plenty of very good reasons to not leave users stuck on unmaintained node versions in the lurch
Could you be able to tell me some of them, please?
When someone is on, say, node 4, and wants to upgrade to node 10, that's a risky and costly effort. The best way to derisk it, and make it cheaper/faster, is to first upgrade all deps while still on node 4, which hopefully all work on both node 4 and node 10, and then upgrade the platform after tests are passing. Every dependency that requires updating it at the same time as updating the platform makes the platform upgrade harder, and thus can prevent it from happening at all. Supporting old platforms makes it easier for people to upgrade, not harder.
Fair enought, but here is not about Node.js deprecations, but instead about new EcmaScript functionality available in newer versions of Node.js, and they are backwards compatible. You are right about maintaining documentation of Node.js APIs, and I agree about having a checkbox to show the unmaintained versions, just only having it enable by default to show all versions is superfluous.
Indeed; I was responding to
Nobody should be worrying for something older than Node.js 8.x anyway... :-)
Oh, sure, but in that case, it's responsability of the developer to have it's project dependencies and environment updated without waiting until It gets unmaintained and deprecated... :-/
It's also their prerogative to keep using something even if its maintainers have abandoned it.