Update Node Version
Developmentupdate-node-versionUpdate Node Version is an Agent Skill for development published in the help-me-mom/ng-mocks repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when updating major Node.js versions across ng-mocks projects, including CI/CD, .nvmrc, Docker images, npm compatibility, @types/node, and wrapper-based validation.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/help-me-mom/ng-mocks/blob/HEAD/.agents/skills/update-node-version/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-node-version, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Update Node Version
Use this skill when the request is to update major Node.js version across some or all of the repository.
Task List
Begin with a plain Markdown checklist that works in AI Agent:
- [ ] Identify which projects should move to the new Node line
- [ ] Inspect all current Node, npm, Docker, and type-version declarations
- [ ] Update the affected config and package files together
- [ ] Re-bootstrap dependencies with wrapper commands
- [ ] Run wrapper-based validation on every changed target
- [ ] Summarize the new version mapping and any compatibility limits
Workflow
- Determine the scope:
- projects which don't belong to a particular angular major version,
- specific versioned Angular fixtures,
- or the whole repo.
- Inspect the current version mapping in:
- root
.nvmrc,docs/.nvmrc,tests-e2e/.nvmrc, and affectede2e/*/.nvmrc compose.yml.circleci/config.ymland any CI workflow that pins a Node version- root, docs, tests-e2e, and affected e2e
package.jsonfiles
- root
- Keep related version declarations aligned:
- Docker image tag
.nvmrcnpmversionengines.npm@types/nodewhere applicable
- Do not assume every Angular fixture can move to the newest Node major. Preserve per-target compatibility unless the task explicitly changes that support boundary.
- Re-bootstrap changed targets with
sh compose.sh <target>. - Validate with
sh test.shfor root, e2e, and every changed target. - If changing dependency metadata requires a lockfile refresh, use the
update-package-locksskill instead of an ad-hoc npm command.
Commands
# Bootstrap changed targets with a unique compose namespace.
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh root
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh e2e
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh <target>
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh compose.sh docs
# Validate changed targets.
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh root
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh e2e
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh <target>
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> docker compose run --rm docs npm run build
Validation
COMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh rootCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh e2eCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> sh test.sh <target>for each target whose Node line changedCOMPOSE_PROJECT_NAME=ngmocks_node_<unique> docker compose run --rm docs npm run buildwhen the docs Node line changed
Guardrails
- Never assume the root Node version should also be used by every legacy Angular fixture.
- Never use local
npm install,npm update, or ad-hocnodecommands for validation when wrapper commands exist. - Keep npm compatibility aligned with the chosen Node version.
- Use one unique
COMPOSE_PROJECT_NAMEfor all commands in the same worktree. - If a commit is requested for a pure Node-image update, use
chore(docker): updating node images.