[contributor-docs] Add guidance for Node version support in projects
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- node.js
- Domain
- documentation
Research direction
No file, test, or entry point is named. Start by reviewing the linked Node.js release cadence and research the risks of EOL versions. Done means contributor guidance covers development, CI, production, OSS minimum versions, odd-numbered releases, and how projects should stay current over time.
Written by the indexing model from the issue text.
Description
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?
- Dominant language
- JavaScript
- Stars
- 86
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/contributor-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
MetaMask/contributor-docs#164 ·
-
category-documentation github-migration-triaged team-wallet-framework wf-documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MetaMask/contributor-docs#115 · 1 comment ·
-
issue Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
MetaMask/contributor-docs#169 ·
-
team-core-platform
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MetaMask/contributor-docs#157 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
MetaMask/contributor-docs#142 ·
All issues in MetaMask/contributor-docs
Similar issues
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#122386 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
docs web/
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100