- Home
- Skills
- Code Quality & Review
- npm Upgrade Preflight: Node & Peer Dependency Checks
npm Upgrade Preflight: Node & Peer Dependency Checks
Check selected npm target versions against Node.js requirements and direct peer constraints. Separate declared ranges from lockfile versions, then deliver evidence and a verification plan.
$1
Works with the AI Agents you already use
npm Upgrade Preflight: Node & Peer Dependency Checks
Example session with this skill installed
Preflight the official Vite vanilla-ts template at commit 5f52bc8b9e4090cdcaf3f704278db30dafc825cc. Its manifest declares vite ^5.4.2. Check the explicit historical target vite@7.0.0 with planned Node 18.20.8, then repeat with Node 20.19.0 using the same manifest, targets and registry snapshot. Do not install or edit dependencies or run project scripts. Show what conflicts, what remains unverified and which existing verification commands have not run.
- Read your context and instructions
- Compiled the npm upgrade preflight
- Generated the document
Executed Vite metadata preflight
The input was an unmodified package.json from Vite's official vanilla-ts template at fixed commit 5f52bc8b9e4090cdcaf3f704278db30dafc825cc. It declares vite ^5.4.2 and typescript ^5.5.3. The target 7.0.0 is an explicit historical test version, not a latest-version recommendation. One live request retrieved matching public npm version metadata; the second check reused its saved snapshot.
| Planning input | Vite target Node requirement | Result | CLI exit |
|---|---|---|---|
| Node 18.20.8 | ^20.19.0 OR >=22.12.0 | Declared engine conflict | 1 |
| Node 20.19.0 | Same metadata | Declared engine matches | 0 |
Findings retained in both reports
- Target 7.0.0 is outside the declared ^5.4.2 range. A deliberate manifest edit is required; this does not prove API breakage.
- No lockfile was provided. The actual installed baseline is unknown; the checker did not treat 5.4.2 as an installed version.
- All eleven declared target peers were optional and absent from the template's root dependencies. None was falsely treated as a missing-required-peer conflict.
- The manifest defines npm run build with body tsc && vite build. This command was listed but NOT RUN. No test script was defined, so the verification gap was reported.
- Package installation, manifest edits, lockfile regeneration and source-code compatibility were NOT performed or verified.
The Node 18 report contained 1 conflict, 1 review and 1 unverified check. The Node 20.19 report contained 0 conflicts, while the same 1 review and 1 unverified check remained. Exit 0 means the defined preflight conditions completed, not that an upgrade or project build succeeded. Both audits actually ran on Node 25.6.1; the two Node versions above were comparison inputs, not runtimes installed or switched during testing.
Delivered files and verification
Each run produced report.html, report.json, upgrade-plan.md and metadata-snapshot.json. Manifest and target hashes matched before and after, and both runs used identical metadata. The reports keep the original declaration, target version, peer evidence, metadata identity and unexecuted validation commands separately.
An independent set of seventeen offline CLI checks also matched expected outcomes. It covered caret-zero/OR/prerelease ranges, missing optional versus required peers, present optional peer conflicts, overlapping peer ranges, linked target selections, valid/stale lockfile evidence, invalid metadata, HTML escaping, unchanged inputs, no repository-script execution, no network use in snapshot mode and independent temporary-script execution.
Interpretation
This validates a real open-source manifest and registry-metadata preflight plus deterministic local checks. It does not demonstrate an installed upgrade, a successful Vite build, vulnerability status, deployment readiness or a complete npm resolution. The unresolved declaration/baseline items still need review before any separately approved upgrade.
report.html
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Check the upgrade assumptions before editing dependencies
A target release can require a newer Node.js runtime or different peer versions. This executable preflight checks those declared constraints and shows what is known, what conflicts and what still needs verification.
What you provide
- A root npm package.json.
- One to ten selected direct dependencies with explicit target versions.
- A concrete planned Node.js version.
- Optional: a root npm v2/v3 package-lock.json.
What you receive
- HTML and JSON reports with per-package evidence and input hashes.
- An upgrade-plan.md with required declaration changes, peer review items and existing project validation commands.
- A public-registry metadata snapshot for repeatable offline checks.
Checks that preserve the distinction
A manifest range is not an installed version. A lockfile can supply a resolved baseline when valid. A target outside the current range needs review and an edit; it does not automatically prove source-code breakage. A peer-range intersection is only possible overlap. Missing optional peers are accepted as absent; present optional peers are checked. Missing required peers remain unresolved because npm can install peers automatically.
Executed examples
A real official Vite template and live public-registry metadata reproduced a Node engine conflict. Changing only the planned Node input removed that conflict while preserving unresolved review items. Seventeen independent offline CLI checks also matched expected outcomes. No package installation or project build was claimed.
Clear limits
This is a root dependency metadata preflight. It does not install packages, change manifests or lockfiles, run repository scripts, solve the complete dependency tree, scan vulnerabilities or prove API compatibility. Project build/test/lint commands are listed only when defined, and remain unexecuted. The Node version is a planning input, not a runtime switched by this tool.
Node.js 18+ and semver 7 are required. Live mode reads selected version metadata from the public npm registry; snapshot mode is local. A temporary Agensi script may need NODE_PATH pointing to an existing node_modules directory. Dependencies are not bundled. The $1 one-time purchase covers the skill, not hosted execution or an automatic upgrade service.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Root npm metadata checks only. No full resolver, workspace traversal, transitive analysis, private-registry authentication, source API compatibility, vulnerability scan, install or build execution. Planned Node version is not the audit runtime. Review/unverified checks may remain even with exit 0.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
Node.js 18+semver 7
Needs terminal and local files. Live checks access the public npm registry. Set NODE_PATH for the invocation if semver is in an existing project/global dependency directory.
Permissions
Reads the chosen manifest, targets and optional lockfile. Sends only selected package names/target versions to registry.npmjs.org. Writes local reports/snapshot. Uses NODE_PATH when needed; does not read npm credentials, install packages, execute repository scripts or modify inputs.