Closed slifty closed 2 years ago
From Node survey in 2018:
Most Node [76%] users use a version manager – typically Nvm [52%]. ... There has been a drop in those who say the LTS schedule support timeframe is ‘clear’, down to just half of users. Those least likely to see as clear are front-end developers, APAC and those in smaller companies. ... Importantly, only a minority of new users report a good understanding of the LTS schedule/support timeframe. ... More than half of users rely on LTS release line – but that number is slipping. ... Current is particularly popular among small companies, and newer Node users.
So to summarize, people think LTS is important to have, but many, likely including those in our target audience, use the latest release instead and may not really understand the release schedule. Makes sense. My guess is those folks could lag a major version until nagged to upgrade. Once they do, many say they use a package manager (though the population that use non-nvm managers is hella fragmented and it may be harder for them to easily switch between versions on the fly).
Given that, I think it's okay to still support 13 for a while if it's not too hard to do so, but it's also okay to drop it in the near future if supporting it becomes a pain. 12, as the current LTS, would be good to have, but you wait long enough and 14 will be LTS, so it's not essential and again, if it's a pain, maybe don't bother.
But if you want to, for instance, ship a Docker image, for which I am planning to make an issue, maybe use 14.
Pinning to LTS seems like a sensible idea, assuming downgrading us to 12 today doesn't cause any problems. Unless we actually require newer features, LTS seems like a good signal of conservative technical stability.
13 is now EOL. I think a strong argument for 14 is future proofing. It'll be LTS until 2023.
I'm down with that. It doesn't start LTS until October but I… don't think we're taking a terrible risk by adopting it before then. 👍
I think 14 is a great move by the way -- I also think we may want to move this to meta since it spans all of our repos.
On a related note -- since this is now a library we should actually figure out the lowest node version that it will support. We want folks to be able to incorporate TVK functionality into existing projects which may be on earlier versions of node than 14.x
I made a duplicate issue #23 which is now complete!
Task
Description
@chriszs just pointed out that Node 13 is reaching EOL in a few days and that Node 14 will be the next LTS.
We should either move to Node 14 or back to Node 12.
Relevant Resources / Research
No
Related Issues
No