TypeScript 2,604 FILES 6 FINDINGS

HOW SVELTEKIT
ACTUALLY WORKS

Web development, streamlined. The framework for building Svelte apps. Conventions, patterns, and architecture extracted from the sveltejs/kit repository by sourcebook.

VIEW_REPO north_east

QUICK_REF:

Build: pnpm --filter '@sveltejs/*' -r build Lint: pnpm -r lint

WHAT_MATTERS

→
This is a monorepo — check workspace dependencies before modifying shared code
→
packages/kit/src/utils/filesystem.js is a hub file (imported by 18 files) — changes here ripple everywhere
→
21 dead code candidates detected

KEY_FINDINGS

This is a monorepo. Changes may affect multiple packages. Check workspace dependencies before modifying shared code.

HIGH

Tests are co-located with source files (*.test.ts next to *.ts). Keep this pattern.

HIGH

Project uses barrel exports (index.ts files that re-export). Import from the directory, not from deep paths.

HIGH

19 barrel export files found

Hub files (most depended on): packages/kit/src/utils/filesystem.js (18 files); packages/kit/src/utils/functions.js (17 files); packages/kit/src/core/sync/utils.js (13 files); packages/kit/src/runtime/utils.js (12 files); packages/kit/src/runtime/shared.js (12 files). Changes here have the widest blast radius.

HIGH

Circular imports: fetch.js → respond.js. Avoid adding to these cycles.

HIGH

21 dead code candidates.

HIGH

smart_toy USING_AI_TOOLS

→this is a monorepo — check workspace dependencies first
→check file importance before editing hub files
→follow existing barrel export patterns

CLAUDE.MD expand_more

# CLAUDE.md

This file provides guidance to Claude Code when working with this codebase.
Generated by [sourcebook](https://github.com/maroondlabs/sourcebook). Review and edit — the best context comes from human + machine together.

## Commands

- **Build:** `pnpm --filter '@sveltejs/*' -r build`
- **Lint:** `pnpm -r lint`

## Stack

TypeScript

## Core Modules (by structural importance)

- `packages/kit/src/runtime/utils.js`
- `packages/kit/src/utils/filesystem.js`
- `packages/kit/src/utils/functions.js`
- `packages/kit/src/runtime/client/client.js`
- `packages/kit/src/utils/url.js`

## Critical Constraints

- **Monorepo:** This is a monorepo. Changes may affect multiple packages. Check workspace dependencies before modifying shared code.
- **Testing:** Tests are co-located with source files (*.test.ts next to *.ts). Keep this pattern.
- **Core modules:** Hub files (most depended on): packages/kit/src/utils/filesystem.js (18 files); packages/kit/src/utils/functions.js (17 files); packages/kit/src/core/sync/utils.js (13 files); packages/kit/src/runtime/utils.js (12 files); packages/kit/src/runtime/shared.js (12 files). Changes here have the widest blast radius.
- **Circular dependencies:** Circular imports: fetch.js → respond.js. Avoid adding to these cycles.

## Conventions & Patterns

- **Import conventions:** Project uses barrel exports (index.ts files that re-export). Import from the directory, not from deep paths.

## Before Making Changes

- **Check file importance** before editing. Hub files (listed in Core Modules) affect many other files — changes here have the widest blast radius.
- **Follow existing patterns.** This project has established conventions (listed above). Match them instead of introducing new approaches.
- **Respect constraints.** Review the Critical Constraints section before making structural changes.

If the sourcebook MCP server is available (`sourcebook serve`), verify before acting:
- `get_blast_radius` — check what breaks if you edit a hub file
- `query_conventions` — confirm the right pattern before adding new code
- `get_pressing_questions` — get a briefing before editing an unfamiliar file

## What to Add Manually

The most valuable context is what only you know. Add:

- Architectural decisions and why they were made
- Past incidents that shaped current conventions
- Deprecated patterns to avoid in new code
- Domain-specific rules or terminology
- Environment setup beyond what .env.example shows

GENERATED IN ~3 SECONDS WITH

npx sourcebook init

VIEW ON GITHUB star

FROM_THE_BLOG

Why AI agents fail on real codebases arrow_forward Why auto-generated context makes agents worse arrow_forward

RELATED_REPOS

NEXT.JS ASTRO

HOW SVELTEKITACTUALLY WORKS

WHAT_MATTERS

KEY_FINDINGS

npx sourcebook init

FROM_THE_BLOG

RELATED_REPOS

HOW SVELTEKIT
ACTUALLY WORKS