node

Pin Node version 25 in .nvmrc for consistent CI tooling.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/matthewharwood/dean-stack --skill node-matthewharwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node
Source: https://github.com/matthewharwood/dean-stack/tree/main/.claude/skills/node
Command: npx skills add https://github.com/matthewharwood/dean-stack --skill node-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pinning Node version 25 for tooling in a Bun-first development environment so CI and build tooling run consistently while the app runtime remains static on GitHub Pages.

Core Features & Use Cases

  • Ensures a single source of truth for the Node version via .nvmrc.
  • Enables CI tooling by coordinating with actions/setup-node and Bun-based workflows.
  • Keeps the application runtime Node-free, using Node only for tooling and build steps.

Quick Start

Pin Node 25 via the repository's .nvmrc and ensure CI tooling uses Node only for tooling tasks.

Frequently Asked Questions about node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pin Node version 25 for Bun-based CI tooling?

Pin Node 25 for Bun-based CI tooling by specifying the version in your repository's .nvmrc file and integrating it with actions/setup-node. This ensures tooling runs consistently across environments while the app runtime remains statically served.

When do I need to pin Node in a Bun-first development environment?

Pin Node in a Bun-first environment when tools refuse to run on Bun or when Node-based tooling must execute during CI. This policy ensures Node is used strictly for tooling and build steps, not as a runtime target.

Does this approach work with GitHub Actions and actions/setup-node?

Yes, this approach works with GitHub Actions and actions/setup-node by coordinating CI workflows. It keeps the application runtime Node-free on GitHub Pages while using Node only for tooling and build steps.

What's the best way to ensure consistent Node versions across CI environments?

The best way to ensure consistent Node versions across CI environments is using a .nvmrc file as a single source of truth. Coordinating this with actions/setup-node guarantees Node-based tooling executes consistently.

Why should Node be tooling-only and not a runtime target in Bun workflows?

Node should be tooling-only and not a runtime target in Bun workflows to ensure the app runtime remains static on GitHub Pages. Using Node strictly for tooling prevents runtime conflicts and maintains a Node-free deployment.