You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[contributor-docs] Add guidance for Node version support in projects #63
We should make sure that the company is on the same page about how Node versions ought to be specified in projects and which versions of Node we ought to support.
What version(s) of Node.js should be run in a development, CI, or production environment? Evaluate risk of running EOL Node.js versions in these environments.
For OSS projects, should the minimum supported Node.js version track the above? When can OSS projects drop an old version of Node.js, when should they, and when must they?
Any special considerations for odd-numbered releases? These versions do not enter LTS and have a lifespan of about nine months.
Given Node.js has a [documented release cadence|https://github.com/nodejs/release] — a version going EOL should not be a surprise — how should projects use this info to stay within the guidelines over time?
what the engines.node field in package.json represents and how that relates to the current, past, and future versions of Node (considering that Yarn v2+ ignores it by default when installing dependencies)
what .nvmrc represents and what its relationship to engines.node is
how the versions of Node we test (i.e. the matrix we use in CI) relate to both of these
Perhaps we ought to use this space to clarify these as well?
changed the title [-]Add guidance for Node version support in projects[/-][+][contributor-docs] Add guidance for Node version support in projects[/+]on May 19, 2026
Elliot Winkler commented: This is still somewhat relevant. It’s lower priority because while {{engines.node}} isn’t enforced and is therefore ceremonial, it doesn’t really cause any issues, because we don’t update the Node version that often in our projects, and when we do update it, it’s not difficult to understand which version to switch to. That said, it would be nice to clarify our policy once and for all somewhere in case anyone gets confused.
Activity
mcmire commentedon Jun 12, 2024
We've also had questions around:
engines.nodefield inpackage.jsonrepresents and how that relates to the current, past, and future versions of Node (considering that Yarn v2+ ignores it by default when installing dependencies).nvmrcrepresents and what its relationship toengines.nodeisPerhaps we ought to use this space to clarify these as well?
[-]add guideline: Node.js version usage & support[/-][+]Add guidance for Node version support in projects[/+][-]Add guidance for Node version support in projects[/-][+][contributor-docs] Add guidance for Node version support in projects[/+]exalate-issue-sync commentedon May 19, 2026
Elliot Winkler commented: This is still somewhat relevant. It’s lower priority because while {{engines.node}} isn’t enforced and is therefore ceremonial, it doesn’t really cause any issues, because we don’t update the Node version that often in our projects, and when we do update it, it’s not difficult to understand which version to switch to. That said, it would be nice to clarify our policy once and for all somewhere in case anyone gets confused.