Node.js Runtime & Version Management Install and reason about the JavaScript runtime as a controlled dependency, not a mysterious global prerequisite.
Book 2 · Node runtime Course baseline: September 17, 2026 · Windows-first · Project-driven · Production-oriented
Contents 1. Why Node comes first 6. PowerShell shell setup
Phase 01 | Page 2 of 6
Node.js is the runtime beneath our JavaScript tooling Next.js, NestJS, pnpm, Prisma tooling, test runners, build systems, and many developer utilities ultimately run on Node.js. If the runtime is wrong, every layer above it can become confusing.
Figure 1 - Why Node comes before frameworks - Framework commands are programs running on a specific Node runtime, not independent magic.
Why use LTS instead of Current?
As of September 17, 2026, Node 24.21.0 is an LTS release while Node 26 is the Current line. This course chooses the LTS line because a long multi-phase curriculum benefits from stability and ecosystem compatibility more than early access to the newest runtime features.
Why use a version manager?
Installing one global Node version seems simpler until project A requires Node 24 and a future experiment requires Node 26. A version manager turns runtime selection into an explicit action.
Phase 01 | Page 3 of 6
Project requirements → fnm → Selected Node version →
node.exenode -v
npm -v
Get-Command node -ErrorAction SilentlyContinue
Get-Command npm -ErrorAction SilentlyContinueIf Node already exists, do not immediately uninstall it. First learn where it came from.
winget install Schniz.fnm
fnm --version
fnm works by updating environment variables for the shell. The official project recommends evaluating fnm env for the current shell. For a PowerShell profile, a common setup is:
if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force } notepad $PROFILE
Add the shell-initialization line appropriate to the installed fnm version, based on fnm env --shell powershell . Reopen PowerShell and verify fnm --version .
PowerShell profiles are personal configuration files. Inspect them before editing. A course should never erase existing developer configuration just to add one tool.
Phase 01 | Page 4 of 6
fnm install 24.21.0 fnm use 24.21.0 node -v npm -v
v24.21.0 11.19.0
Later we can place a runtime version file in the repository. For now, the important skill is being able to select and verify the runtime explicitly.
npm ships with Node and serves two roles: package registry client and project/package command tool. In this course we will use pnpm as the primary package manager, but npm remains useful for bootstrapping pnpm into the user profile when needed.
fnm works, but node does not change The shell environment probably has not loaded fnm's environment changes. Inspect fnm env --shell powershell , your PowerShell profile, and Get-Command node .
Wrong Node after opening a new terminal Check whether fnm initialization loads in that new shell and whether another Node path appears earlier on PATH.
Company machine blocks WinGet Use an approved installer mechanism from IT or the fnm release binary. The engineering principle stays the same: install in user-accessible locations and make PATH explicit.
Phase 01 | Page 5 of 6
□ fnm --version works. □ fnm use 24.21.0 works. □ node -v is v24.21.0. □ npm -v is 11.19.0. □ Get-Command node points to the runtime selected through fnm.
Phase 01 · Book 2 · Node runtime
Phase 01 | Page 6 of 6
Node Runtime and Version Management matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Node Runtime and Version Management” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: source file → tool/runtime → process → OS environment → terminal evidence. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: A verified toolchain report showing shell, Git, Node, Corepack/pnpm, editor, PATH, ports, and diagnostic commands.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
Input -> owner -> transformation -> observable output -> failure evidenceDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Node Runtime and Version Management” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Install or verify Git and VS Code with user-level installation where possible.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.EPERM caused by writing to protected locations
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.