How do their routing APIs compare? Cite files from both repos.

The search returned more SvelteKit results. Unfortunately, the repository_data block only contains a README header stub for vercel/next.js, with no actual routing implementation to compare. Let me provide what I can from the SvelteKit side:

SvelteKit Routing API

sveltejs/kit exposes a filesystem-based routing API with two main functions in packages/kit/src/runtime/app/paths/client.js:

1. resolve() [L54-L70]: Resolves a pathname or route ID with dynamic parameters. It enforces absolute paths starting with / and combines them with a base path. Example: resolve('/blog/[slug]', { slug: 'hello-world' }).

2. match() [L89-L107]: Matches a path/URL to a route ID and extracts parameters. Returns { id: RouteId, params: Record<string, string> } or null. Example: await match('/blog/hello-world') returns { id: '/blog/[slug]', params: { slug: 'hello-world' } }.

Route patterns use bracket syntax:

• [param] for dynamic segments
• [[optional]] for optional segments
• [...rest] for rest parameters
• Route conflict detection prevents overlapping routes [packages/kit/src/core/sync/create_manifest_data/conflict.js:L2-L55]

Next.js Routing API

The repository_data block provides no Next.js source code — only a README header. I cannot cite specific Next.js routing files or functions to compare. To properly compare both frameworks' routing APIs, I would need actual Next.js implementation code.

For a detailed comparison, you'd want to ask: What specific routing features interest you? (e.g., parameter extraction, route matching, conflict prevention, optional segments)

FOLLOW_UPS:

• How does SvelteKit handle dynamic segment matching?
• What matchers does SvelteKit support for route parameters?
• Does SvelteKit validate route patterns at build time?