docs: require Node 26 for local setup

Open Beginner friendly
#1,574 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@majestic-owl448 is already working on this.

Since Oct 13, 2026.

  • #1586 by @majestic-owl448 — open

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, node.js
Domain
documentation

Research direction

Read the two named pages: src/content/docs/how-to-setup-freecodecamp-locally.mdx and src/content/docs/troubleshooting-development-issues.mdx. First confirm that freeCodeCamp/freeCodeCamp#70714 has merged and check whether Node 26 is Active LTS at that time. Update both Node 24 references to Node 26, keeping “Active LTS” only if accurate; leave the docs site's own Node version out of scope.

Written by the indexing model from the issue text.

Description

freeCodeCamp/freeCodeCamp#70714 moves freeCodeCamp/freeCodeCamp to Node 26 (.nvmrc, engines.node: ">=26"). Two pages still require Node 24:

  • src/content/docs/how-to-setup-freecodecamp-locally.mdx: the prerequisites table lists Node.js 24.x, "The Active LTS version".
  • src/content/docs/troubleshooting-development-issues.mdx: "Your operating system must support Node.js 24."

Proposal, when freeCodeCamp/freeCodeCamp#70714 merges:

  • Change both pages to Node.js 26.
  • Keep "Active LTS" only if Node 26 is Active LTS at that time. Node 26 enters LTS on 2026-10-28.

The docs site's own Node version (how-to-work-on-the-docs-site.mdx, .devcontainer, CI) is out of scope.

Dominant language
MDX
Stars
161
Forks
404
Avg merge
3h 43m
Merged PRs (30d)
55

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freeCodeCamp/contribute

All issues in freeCodeCamp/contribute

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.