{"owner":"nitrojs","repo":"nitro","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/copilot-instructions.md"],"skills":{"AGENTS.md":"## Project Identity\n\nNitro is a framework-agnostic and deployment-agnostic server framework powered by [H3](https://github.com/h3js/h3) (v2), [UnJS] (https://github.com/unjs), and Vite | Rolldown | Rollup.\n\n## First-time Setup for Development\n\n- Run `corepack enable` to ensure `pnpm` is available.\n- Run `pnpm install` to install dependencies.\n- Run `pnpm build --stub` to prepare development mode.\n\n## Key Scripts\n\n- `pnpm build --stub` — Fast stub build (`obuild --stub`) for development.\n- `pnpm build` — Full build (`pnpm gen-presets && obuild`).\n- `pnpm lint` — Check lint and formatting (`oxlint` + `oxfmt --check`).\n- `pnpm fmt` — Auto-fix lint and formatting (`automd` + `oxlint --fix` + `oxfmt`).\n- `pnpm test` — Full pipeline: `lint && build && typecheck && test:rollup && test:rolldown` (runs vitest against both the rollup and rolldown builders).\n- `pnpm test:rollup` / `pnpm test:rolldown` — Run vitest against a single builder (`NITRO_BUILDER`).\n- `pnpm typecheck` — Type-check with the TypeScript native-preview compiler (`tsgo --noEmit --skipLibCheck`).\n\n**Always run** `pnpm fmt` and `pnpm typecheck` after making changes.\n\n## Repository Structure\n\n- `.github/` — GitHub Actions workflows.\n- `docs/` — Documentation site built with [UnDocs](https://github.com/unjs/undocs).\n- `examples/` — Example projects and integrations.\n- `src/` — Project source code.\n- `test/` — Unit, minimal, and end-to-end tests.\n\n### Code Structure\n\nProject source is centralized under `src/`:\n\n- `src/build` — Build logic (Vite | Rolldown | Rollup config, virtual templates in `src/build/virtual/`, plugins in `src/build/plugins/`).\n- `src/cli` — `nitro` CLI subcommands (each file in `src/cli/commands` is a command).\n- `src/config/` — Config defaults (`src/config/defaults.ts`) and resolvers/normalizers (`src/config/resolvers`).\n- `src/dev` — Development server logic (`app.ts`, `server.ts`, `vfs.ts`).\n- `src/prerender` — Prerender logic.\n- `src/presets` — Deployment presets and runtime entry.\n- `src/types` — Shared types.\n- `src/utils` — Internal utilities.\n- `src/runtime` — Runtime code that goes into the bundle (runtime and platform agnostic).\n\n### Why Changes in `src/` Are High-Impact\n\nCode in `src/` affects all Nitro users:\n\n- Changes in `src/runtime` are bundled and run across all deployment targets.\n- Changes in `src/build` affect build output and performance.\n- Changes in `src/presets` affect specific deployment platforms.\n- Changes in `src/config` affect default behavior.\n\nReview these changes carefully for backwards compatibility, bundle size, and cross-runtime support.\n\n## Code Patterns & Conventions\n\n- `pathe` — Cross-platform path operations (always prefer over `node:path`).\n- `defu` — Deep object merging and config defaults.\n- `consola` — Logging in build/dev code (use `nitro.logger` when available).\n- `unstorage` — Storage abstraction.\n\n### Runtime Constraints\n\nCode in `src/runtime/` must be runtime-agnostic:\n\n- **Don't use Node.js-specific APIs** (unless behind runtime checks).\n- Prefer **Web APIs** (fetch, Request, Response, URL, etc.).\n- Only use `console` for logging (no `consola` in runtime).\n- Keep bundle size minimal and side-effect free.\n\n## Testing Strategy\n\n### Test Structure\n\nMain tests are defined in `test/tests.ts` and setup per each deployment provider in `test/presets` and run against `test/fixture` nitro app. Add new regression tests to `test/fixture`.\n\nOther tests:\n\n- **Unit** (`test/unit/`) — Isolated unit tests.\n- **Minimal** (`test/minimal/`) — Smallest bundle output.\n\n### Testing Requirements\n\n- Run `pnpm run test` before submitting.\n- **Bug fixes MUST include a failing test first** — add regression tests to `test/fixture/` and make sure test script fails before attempting the fix and resolves after.\n- Keep tests deterministic and environment-independent.\n\n## Working with Presets\n\nEach preset in `src/presets/` defines deployment target behavior:\n\n- Runtime logic and entry is in `src/presets/<name>/runtime`\n- Preset config and utils (build time) are in `src/presets/<name>/*.ts`.\n\n## Development Workflow\n\n### Making Changes\n\n1. Make changes in `src/`.\n2. Run `pnpm stub` if you changed build logic.\n3. Test with `pnpm test`.\n4. Run `pnpm fmt`.\n5. Run `pnpm typecheck`.\n6. Run `pnpm test:rollup` and/or `pnpm test:rolldown` to run vitest against a specific builder.\n\n## Contribution Principles\n\n- Prefer **minimal, targeted changes** over large refactors.\n- Avoid introducing new dependencies unless strictly necessary.\n  Add them to `devDependencies` unless they are required in runtime logic.\n- Be mindful of **bundle size**, startup cost, and runtime overhead.\n- Maintain **backwards compatibility** unless explicitly instructed otherwise.\n- Batch multiple related edits together. Avoid sequential micro-changes.\n- Never modify files outside the scope of the requested change.\n\n## Common Gotchas\n\n- **Don't use Node.js-specific APIs in `src/runtime/`** — Code runs in multiple runtimes (Node, workers, edge).\n- **Virtual modules must be registered** in `src/build/virtual/_all.ts` (one template per file under `src/build/virtual/`).\n- **CLI commands** are in `src/cli/commands/` — Each file exports a command definition.\n- **Runtime size matters** — Check bundle impact with `pnpm build`.\n- **Use `pathe` not `node:path`** — Ensures cross-platform compatibility.\n\n## Error & Logging Guidelines\n\n- Prefer explicit errors over silent failures.\n- Use `nitro.logger` in build/dev code, `consola` as fallback.\n- Use `console` only in `src/runtime/` code.\n- Use warnings for recoverable situations; throw for invalid states.\n- Include actionable context in error messages.\n\n## Documentation Requirements\n\n- Update `docs/` for user-facing changes.\n- Update types and JSDoc for API changes.\n- Examples in `examples/` should reflect best practices and be added for new integrations.\n- Add migration notes for breaking changes.\n\n## Code Conventions\n\n- Use **ESM** and modern JavaScript; use explicit extensions (`.ts`, `.mjs`) in imports.\n- For `.json` imports, use `with { \"type\": \"json\" }`.\n- Avoid barrel files (`index.ts` re-exports); import directly from specific modules.\n- Place non-exported/internal helpers at the end of the file.\n- For multi-arg functions, use an options object as the second parameter.\n- Split logic across files; avoid long single-file modules (>200 LoC). Use `_*` prefix for internal files.\n- Prefer **Web APIs** over Node.js APIs where possible.\n- Do not add comments explaining what the line does unless prompted.\n- Before adding new code, study surrounding patterns, naming conventions, and architectural decisions.\n- Use existing UnJS utilities and dependencies before adding new packages.\n- Keep runtime code minimal and fast.\n\n## Commit Conventions\n\n- Use **semantic commit messages**, lower-case (e.g., `fix(cli): resolve path issue`).\n- Prefer to include scope (e.g., `feat(runtime):`, `fix(build):`).\n- Add a short description on the second line when helpful.\n\n## Detailed References\n\nFor deeper context, see `.agents/`:\n\n- [`.agents/architecture.md`](.agents/architecture.md) — Full architecture: core instance, build system, config resolution, virtual modules, runtime internals, dev server, routing, key libraries.\n- [`.agents/presets.md`](.agents/presets.md) — All presets (multiple deployment targets + internal `_nitro`/`_static`), preset structure, how to create presets, resolution logic.\n- [`.agents/testing.md`](.agents/testing.md) — Test structure, how tests work, adding regression tests, running tests.\n- [`.agents/vite.md`](.agents/vite.md) — Vite build system: plugin architecture (6 sub-plugins), environments API, dev server integration, production build stages, bundler config, HMR, runtime worker.\n- [`.agents/docs.md`](.agents/docs.md) — Docs site: UnDocs structure, the `.docs/` theme layer (imports, styling tokens, content queries), MDC blocks, and content conventions (preset naming, import paths, H3 v2 patterns, common mistakes).\n\nH3 v2 updated docs is at `node_modules/h3/dist/docs/README.md`\n",".github/copilot-instructions.md":"@../AGENTS.md\n\nRefer to [AGENTS.md](../AGENTS.md) for project instructions.\n"},"files":{"AGENTS.md":"## Project Identity\n\nNitro is a framework-agnostic and deployment-agnostic server framework powered by [H3](https://github.com/h3js/h3) (v2), [UnJS] (https://github.com/unjs), and Vite | Rolldown | Rollup.\n\n## First-time Setup for Development\n\n- Run `corepack enable` to ensure `pnpm` is available.\n- Run `pnpm install` to install dependencies.\n- Run `pnpm build --stub` to prepare development mode.\n\n## Key Scripts\n\n- `pnpm build --stub` — Fast stub build (`obuild --stub`) for development.\n- `pnpm build` — Full build (`pnpm gen-presets && obuild`).\n- `pnpm lint` — Check lint and formatting (`oxlint` + `oxfmt --check`).\n- `pnpm fmt` — Auto-fix lint and formatting (`automd` + `oxlint --fix` + `oxfmt`).\n- `pnpm test` — Full pipeline: `lint && build && typecheck && test:rollup && test:rolldown` (runs vitest against both the rollup and rolldown builders).\n- `pnpm test:rollup` / `pnpm test:rolldown` — Run vitest against a single builder (`NITRO_BUILDER`).\n- `pnpm typecheck` — Type-check with the TypeScript native-preview compiler (`tsgo --noEmit --skipLibCheck`).\n\n**Always run** `pnpm fmt` and `pnpm typecheck` after making changes.\n\n## Repository Structure\n\n- `.github/` — GitHub Actions workflows.\n- `docs/` — Documentation site built with [UnDocs](https://github.com/unjs/undocs).\n- `examples/` — Example projects and integrations.\n- `src/` — Project source code.\n- `test/` — Unit, minimal, and end-to-end tests.\n\n### Code Structure\n\nProject source is centralized under `src/`:\n\n- `src/build` — Build logic (Vite | Rolldown | Rollup config, virtual templates in `src/build/virtual/`, plugins in `src/build/plugins/`).\n- `src/cli` — `nitro` CLI subcommands (each file in `src/cli/commands` is a command).\n- `src/config/` — Config defaults (`src/config/defaults.ts`) and resolvers/normalizers (`src/config/resolvers`).\n- `src/dev` — Development server logic (`app.ts`, `server.ts`, `vfs.ts`).\n- `src/prerender` — Prerender logic.\n- `src/presets` — Deployment presets and runtime entry.\n- `src/types` — Shared types.\n- `src/utils` — Internal utilities.\n- `src/runtime` — Runtime code that goes into the bundle (runtime and platform agnostic).\n\n### Why Changes in `src/` Are High-Impact\n\nCode in `src/` affects all Nitro users:\n\n- Changes in `src/runtime` are bundled and run across all deployment targets.\n- Changes in `src/build` affect build output and performance.\n- Changes in `src/presets` affect specific deployment platforms.\n- Changes in `src/config` affect default behavior.\n\nReview these changes carefully for backwards compatibility, bundle size, and cross-runtime support.\n\n## Code Patterns & Conventions\n\n- `pathe` — Cross-platform path operations (always prefer over `node:path`).\n- `defu` — Deep object merging and config defaults.\n- `consola` — Logging in build/dev code (use `nitro.logger` when available).\n- `unstorage` — Storage abstraction.\n\n### Runtime Constraints\n\nCode in `src/runtime/` must be runtime-agnostic:\n\n- **Don't use Node.js-specific APIs** (unless behind runtime checks).\n- Prefer **Web APIs** (fetch, Request, Response, URL, etc.).\n- Only use `console` for logging (no `consola` in runtime).\n- Keep bundle size minimal and side-effect free.\n\n## Testing Strategy\n\n### Test Structure\n\nMain tests are defined in `test/tests.ts` and setup per each deployment provider in `test/presets` and run against `test/fixture` nitro app. Add new regression tests to `test/fixture`.\n\nOther tests:\n\n- **Unit** (`test/unit/`) — Isolated unit tests.\n- **Minimal** (`test/minimal/`) — Smallest bundle output.\n\n### Testing Requirements\n\n- Run `pnpm run test` before submitting.\n- **Bug fixes MUST include a failing test first** — add regression tests to `test/fixture/` and make sure test script fails before attempting the fix and resolves after.\n- Keep tests deterministic and environment-independent.\n\n## Working with Presets\n\nEach preset in `src/presets/` defines deployment target behavior:\n\n- Runtime logic and entry is in `src/presets/<name>/runtime`\n- Preset config and utils (build time) are in `src/presets/<name>/*.ts`.\n\n## Development Workflow\n\n### Making Changes\n\n1. Make changes in `src/`.\n2. Run `pnpm stub` if you changed build logic.\n3. Test with `pnpm test`.\n4. Run `pnpm fmt`.\n5. Run `pnpm typecheck`.\n6. Run `pnpm test:rollup` and/or `pnpm test:rolldown` to run vitest against a specific builder.\n\n## Contribution Principles\n\n- Prefer **minimal, targeted changes** over large refactors.\n- Avoid introducing new dependencies unless strictly necessary.\n  Add them to `devDependencies` unless they are required in runtime logic.\n- Be mindful of **bundle size**, startup cost, and runtime overhead.\n- Maintain **backwards compatibility** unless explicitly instructed otherwise.\n- Batch multiple related edits together. Avoid sequential micro-changes.\n- Never modify files outside the scope of the requested change.\n\n## Common Gotchas\n\n- **Don't use Node.js-specific APIs in `src/runtime/`** — Code runs in multiple runtimes (Node, workers, edge).\n- **Virtual modules must be registered** in `src/build/virtual/_all.ts` (one template per file under `src/build/virtual/`).\n- **CLI commands** are in `src/cli/commands/` — Each file exports a command definition.\n- **Runtime size matters** — Check bundle impact with `pnpm build`.\n- **Use `pathe` not `node:path`** — Ensures cross-platform compatibility.\n\n## Error & Logging Guidelines\n\n- Prefer explicit errors over silent failures.\n- Use `nitro.logger` in build/dev code, `consola` as fallback.\n- Use `console` only in `src/runtime/` code.\n- Use warnings for recoverable situations; throw for invalid states.\n- Include actionable context in error messages.\n\n## Documentation Requirements\n\n- Update `docs/` for user-facing changes.\n- Update types and JSDoc for API changes.\n- Examples in `examples/` should reflect best practices and be added for new integrations.\n- Add migration notes for breaking changes.\n\n## Code Conventions\n\n- Use **ESM** and modern JavaScript; use explicit extensions (`.ts`, `.mjs`) in imports.\n- For `.json` imports, use `with { \"type\": \"json\" }`.\n- Avoid barrel files (`index.ts` re-exports); import directly from specific modules.\n- Place non-exported/internal helpers at the end of the file.\n- For multi-arg functions, use an options object as the second parameter.\n- Split logic across files; avoid long single-file modules (>200 LoC). Use `_*` prefix for internal files.\n- Prefer **Web APIs** over Node.js APIs where possible.\n- Do not add comments explaining what the line does unless prompted.\n- Before adding new code, study surrounding patterns, naming conventions, and architectural decisions.\n- Use existing UnJS utilities and dependencies before adding new packages.\n- Keep runtime code minimal and fast.\n\n## Commit Conventions\n\n- Use **semantic commit messages**, lower-case (e.g., `fix(cli): resolve path issue`).\n- Prefer to include scope (e.g., `feat(runtime):`, `fix(build):`).\n- Add a short description on the second line when helpful.\n\n## Detailed References\n\nFor deeper context, see `.agents/`:\n\n- [`.agents/architecture.md`](.agents/architecture.md) — Full architecture: core instance, build system, config resolution, virtual modules, runtime internals, dev server, routing, key libraries.\n- [`.agents/presets.md`](.agents/presets.md) — All presets (multiple deployment targets + internal `_nitro`/`_static`), preset structure, how to create presets, resolution logic.\n- [`.agents/testing.md`](.agents/testing.md) — Test structure, how tests work, adding regression tests, running tests.\n- [`.agents/vite.md`](.agents/vite.md) — Vite build system: plugin architecture (6 sub-plugins), environments API, dev server integration, production build stages, bundler config, HMR, runtime worker.\n- [`.agents/docs.md`](.agents/docs.md) — Docs site: UnDocs structure, the `.docs/` theme layer (imports, styling tokens, content queries), MDC blocks, and content conventions (preset naming, import paths, H3 v2 patterns, common mistakes).\n\nH3 v2 updated docs is at `node_modules/h3/dist/docs/README.md`\n",".github/copilot-instructions.md":"@../AGENTS.md\n\nRefer to [AGENTS.md](../AGENTS.md) for project instructions.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"## Project Identity\n\nNitro is a framework-agnostic and deployment-agnostic server framework powered by [H3](https://github.com/h3js/h3) (v2), [UnJS] (https://github.com/unjs), and Vite | Rolldown | Rollup.\n\n## First-time Setup for Development\n\n- Run `corepack enable` to ensure `pnpm` is available.\n- Run `pnpm install` to install dependencies.\n- Run `pnpm build --stub` to prepare development mode.\n\n## Key Scripts\n\n- `pnpm build --stub` — Fast stub build (`obuild --stub`) for development.\n- `pnpm build` — Full build (`pnpm gen-presets && obuild`).\n- `pnpm lint` — Check lint and formatting (`oxlint` + `oxfmt --check`).\n- `pnpm fmt` — Auto-fix lint and formatting (`automd` + `oxlint --fix` + `oxfmt`).\n- `pnpm test` — Full pipeline: `lint && build && typecheck && test:rollup && test:rolldown` (runs vitest against both the rollup and rolldown builders).\n- `pnpm test:rollup` / `pnpm test:rolldown` — Run vitest against a single builder (`NITRO_BUILDER`).\n- `pnpm typecheck` — Type-check with the TypeScript native-preview compiler (`tsgo --noEmit --skipLibCheck`).\n\n**Always run** `pnpm fmt` and `pnpm typecheck` after making changes.\n\n## Repository Structure\n\n- `.github/` — GitHub Actions workflows.\n- `docs/` — Documentation site built with [UnDocs](https://github.com/unjs/undocs).\n- `examples/` — Example projects and integrations.\n- `src/` — Project source code.\n- `test/` — Unit, minimal, and end-to-end tests.\n\n### Code Structure\n\nProject source is centralized under `src/`:\n\n- `src/build` — Build logic (Vite | Rolldown | Rollup config, virtual templates in `src/build/virtual/`, plugins in `src/build/plugins/`).\n- `src/cli` — `nitro` CLI subcommands (each file in `src/cli/commands` is a command).\n- `src/config/` — Config defaults (`src/config/defaults.ts`) and resolvers/normalizers (`src/config/resolvers`).\n- `src/dev` — Development server logic (`app.ts`, `server.ts`, `vfs.ts`).\n- `src/prerender` — Prerender logic.\n- `src/presets` — Deployment presets and runtime entry.\n- `src/types` — Shared types.\n- `src/utils` — Internal utilities.\n- `src/runtime` — Runtime code that goes into the bundle (runtime and platform agnostic).\n\n### Why Changes in `src/` Are High-Impact\n\nCode in `src/` affects all Nitro users:\n\n- Changes in `src/runtime` are bundled and run across all deployment targets.\n- Changes in `src/build` affect build output and performance.\n- Changes in `src/presets` affect specific deployment platforms.\n- Changes in `src/config` affect default behavior.\n\nReview these changes carefully for backwards compatibility, bundle size, and cross-runtime support.\n\n## Code Patterns & Conventions\n\n- `pathe` — Cross-platform path operations (always prefer over `node:path`).\n- `defu` — Deep object merging and config defaults.\n- `consola` — Logging in build/dev code (use `nitro.logger` when available).\n- `unstorage` — Storage abstraction.\n\n### Runtime Constraints\n\nCode in `src/runtime/` must be runtime-agnostic:\n\n- **Don't use Node.js-specific APIs** (unless behind runtime checks).\n- Prefer **Web APIs** (fetch, Request, Response, URL, etc.).\n- Only use `console` for logging (no `consola` in runtime).\n- Keep bundle size minimal and side-effect free.\n\n## Testing Strategy\n\n### Test Structure\n\nMain tests are defined in `test/tests.ts` and setup per each deployment provider in `test/presets` and run against `test/fixture` nitro app. Add new regression tests to `test/fixture`.\n\nOther tests:\n\n- **Unit** (`test/unit/`) — Isolated unit tests.\n- **Minimal** (`test/minimal/`) — Smallest bundle output.\n\n### Testing Requirements\n\n- Run `pnpm run test` before submitting.\n- **Bug fixes MUST include a failing test first** — add regression tests to `test/fixture/` and make sure test script fails before attempting the fix and resolves after.\n- Keep tests deterministic and environment-independent.\n\n## Working with Presets\n\nEach preset in `src/presets/` defines deployment target behavior:\n\n- Runtime logic and entry is in `src/presets/<name>/runtime`\n- Preset config and utils (build time) are in `src/presets/<name>/*.ts`.\n\n## Development Workflow\n\n### Making Changes\n\n1. Make changes in `src/`.\n2. Run `pnpm stub` if you changed build logic.\n3. Test with `pnpm test`.\n4. Run `pnpm fmt`.\n5. Run `pnpm typecheck`.\n6. Run `pnpm test:rollup` and/or `pnpm test:rolldown` to run vitest against a specific builder.\n\n## Contribution Principles\n\n- Prefer **minimal, targeted changes** over large refactors.\n- Avoid introducing new dependencies unless strictly necessary.\n  Add them to `devDependencies` unless they are required in runtime logic.\n- Be mindful of **bundle size**, startup cost, and runtime overhead.\n- Maintain **backwards compatibility** unless explicitly instructed otherwise.\n- Batch multiple related edits together. Avoid sequential micro-changes.\n- Never modify files outside the scope of the requested change.\n\n## Common Gotchas\n\n- **Don't use Node.js-specific APIs in `src/runtime/`** — Code runs in multiple runtimes (Node, workers, edge).\n- **Virtual modules must be registered** in `src/build/virtual/_all.ts` (one template per file under `src/build/virtual/`).\n- **CLI commands** are in `src/cli/commands/` — Each file exports a command definition.\n- **Runtime size matters** — Check bundle impact with `pnpm build`.\n- **Use `pathe` not `node:path`** — Ensures cross-platform compatibility.\n\n## Error & Logging Guidelines\n\n- Prefer explicit errors over silent failures.\n- Use `nitro.logger` in build/dev code, `consola` as fallback.\n- Use `console` only in `src/runtime/` code.\n- Use warnings for recoverable situations; throw for invalid states.\n- Include actionable context in error messages.\n\n## Documentation Requirements\n\n- Update `docs/` for user-facing changes.\n- Update types and JSDoc for API changes.\n- Examples in `examples/` should reflect best practices and be added for new integrations.\n- Add migration notes for breaking changes.\n\n## Code Conventions\n\n- Use **ESM** and modern JavaScript; use explicit extensions (`.ts`, `.mjs`) in imports.\n- For `.json` imports, use `with { \"type\": \"json\" }`.\n- Avoid barrel files (`index.ts` re-exports); import directly from specific modules.\n- Place non-exported/internal helpers at the end of the file.\n- For multi-arg functions, use an options object as the second parameter.\n- Split logic across files; avoid long single-file modules (>200 LoC). Use `_*` prefix for internal files.\n- Prefer **Web APIs** over Node.js APIs where possible.\n- Do not add comments explaining what the line does unless prompted.\n- Before adding new code, study surrounding patterns, naming conventions, and architectural decisions.\n- Use existing UnJS utilities and dependencies before adding new packages.\n- Keep runtime code minimal and fast.\n\n## Commit Conventions\n\n- Use **semantic commit messages**, lower-case (e.g., `fix(cli): resolve path issue`).\n- Prefer to include scope (e.g., `feat(runtime):`, `fix(build):`).\n- Add a short description on the second line when helpful.\n\n## Detailed References\n\nFor deeper context, see `.agents/`:\n\n- [`.agents/architecture.md`](.agents/architecture.md) — Full architecture: core instance, build system, config resolution, virtual modules, runtime internals, dev server, routing, key libraries.\n- [`.agents/presets.md`](.agents/presets.md) — All presets (multiple deployment targets + internal `_nitro`/`_static`), preset structure, how to create presets, resolution logic.\n- [`.agents/testing.md`](.agents/testing.md) — Test structure, how tests work, adding regression tests, running tests.\n- [`.agents/vite.md`](.agents/vite.md) — Vite build system: plugin architecture (6 sub-plugins), environments API, dev server integration, production build stages, bundler config, HMR, runtime worker.\n- [`.agents/docs.md`](.agents/docs.md) — Docs site: UnDocs structure, the `.docs/` theme layer (imports, styling tokens, content queries), MDC blocks, and content conventions (preset naming, import paths, H3 v2 patterns, common mistakes).\n\nH3 v2 updated docs is at `node_modules/h3/dist/docs/README.md`\n","category":"root","tokens":2007},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"@../AGENTS.md\n\nRefer to [AGENTS.md](../AGENTS.md) for project instructions.\n","category":".github","tokens":19}]}