nitro

Enforce GitHub Pages deployment contracts for Nitro v3 static builds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nitro v3 in dean-stack — driven internally by TanStack Start, NOT via a standalone nitro.config.ts. Owns the GH Pages base-path env contract (BASE_PATH), the SPA-fallback 404.html, the .nojekyll marker, and the prerender→dist/client/ output. Triggers on: nitro, github_pages, BASE_PATH, baseURL, prerender, SPA fallback 404, .nojekyll, GH Pages deploy.

Core Features & Use Cases

  • Owns the BASE_PATH environment contract — the canonical channel that drives Vite's base and therefore every emitted asset URL across GitHub Pages deployments.
  • Manages the post-Vite-build steps that turn dist/client/ into a GH-Pages-compliant payload: copy dist/client/index.html to dist/client/404.html and touch dist/client/.nojekyll.
  • Defers to TanStack Start, Vite, and Nitro v3 tooling for app-level prerendering and deployment gating.

Quick Start

Use Nitro v3 integration to ensure the static build artifacts are correctly prepared and deployed to GitHub Pages with the base path contract.

Frequently Asked Questions about nitro

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

FAQPage Schema
How do I deploy a static build to GitHub Pages using Nitro v3?

Deploying a static build to GitHub Pages using Nitro v3 requires synchronizing base-path management, prerender output handling, and SPA fallback readiness to satisfy CI/CD deployment contracts.

Why do my prerendered asset URLs break on GitHub Pages?

Prerendered asset URLs break on GitHub Pages when the BASE_PATH environment contract is not correctly synced to Vite's base, causing every emitted asset URL to resolve incorrectly across deployments.

Do I need a .nojekyll file for my GitHub Pages SPA fallback?

Yes, you need a .nojekyll file for your GitHub Pages SPA fallback to prevent Jekyll processing. Managing this marker alongside copying index.html to 404.html ensures SPA fallback readiness.

Can I use TanStack Start with Nitro v3 for GitHub Pages deployment?

Yes, you can use TanStack Start with Nitro v3 for GitHub Pages deployment. The workflow defers app-level prerendering and deployment gating to TanStack Start, Vite, and Nitro v3 tooling.

What is the best way to manage base paths for static builds across multiple GitHub Pages apps?

The best way to manage base paths for static builds across multiple apps is enforcing a canonical BASE_PATH environment contract that drives Vite's base configuration for consistent asset URL emission.

Why is my 404.html not working on GitHub Pages with a static build?

Your 404.html might not work on GitHub Pages if the post-Vite-build steps are missing. Copying dist/client/index.html to dist/client/404.html and touching .nojekyll ensures SPA fallback readiness.