Replies: 4 comments 2 replies
-
Shouldn’t we wait until Vercel supports v14? They are blocked by AWS Lambda vercel/vercel#4754 |
Beta Was this translation helpful? Give feedback.
-
I think the proposed solution sounds good, but I also agree with @michalsanger that we should wait until vercel supports v14, since we have code running there 🙂 |
Beta Was this translation helpful? Give feedback.
-
Vercel supports v14 now: https://vercel.com/changelog/node-js-14-lts-is-now-available |
Beta Was this translation helpful? Give feedback.
-
Done: #1718 |
Beta Was this translation helpful? Give feedback.
-
Node.js 12 is currently "maintenance LTS" (https://nodejs.org/en/about/releases/) and instead, there is Node.js 14 (active LTS). There is also Node.js 15 (current) and Node.js 16 coming soon.
At this moment, we actively support versions 12, 14, and 15. According to Node.js recommendations, production applications should only use active LTS or maintenance LTS releases. This requirement would be fulfilled even with the removal of Node.js 12. So, I'd like to propose removing Node.js 12 and supporting only versions 14, 15 (and 16 when it's ready).
Questions
How should we do the deprecation? We can safely ignore packages with
0.x
, however, other packages would need to be released with a major bump. Is this the right way to go? How would you do it? What should we write to the changelog?Does anyone depend on Node.js 12 and require extra time for the migration?
Proposal
CHANGELOG.md
files of all packages (please help me with the wording):Alternatives
Beta Was this translation helpful? Give feedback.
All reactions