chore: support Node.js v20 engine #48
Conversation
closes: #45 Signed-off-by: Rifa Achrinza <[email protected]>
| }, | ||
| "engines": { | ||
| "node": "14 || 16 || 17 || 18 || 19" | ||
| "node": "14 || 16 || 17 || 18 || 19 || 20" |
There was a problem hiding this comment.
@achrinza any reason why you can't put >=14 here so it will work for 21, 22, ... too?
There was a problem hiding this comment.
Hi Jokay,
It was decided to explicitly list tested Node.js versions to give users a general recommendation on which Node.js versions are officially supported by the package.
Although some details are outdated (e.g. we now test against non-LTS versions), the rationale behind this decision can be found at #29 (comment).
Basically it stems from a disagreement between Yarn and NPM on how to treat engines.node in package.json. In this case, Yarn does provide ways to mimic NPM's more permissive approach if necessary.
We also believe most users will be sticking to LTS versions of Node.js. Since there is ample time between a Node.js release being promoted from "Current" to "LTS", we think this is a good tradeoff.
Hope it helps!
closes: #45