How does the App Router resolve a route? Cite source files.

Unfortunately, the search results aren't returning the core App Router route resolution implementation. The repository data provided focuses on caching patterns, documentation mapping, and testing infrastructure rather than the internal routing logic.

Based on what's available in the repository data, I can see references to nested route structures and dynamic segment handling (like [region], [category], [productId]) in [.claude-plugin/plugins/cache-components/skills/cache-components/PATTERNS.md:L605-L680], which shows how the App Router handles hierarchical routes with parameters, but this is an example of routing patterns rather than an explanation of the resolution algorithm itself.

To properly answer your question about how the App Router resolves routes, I would need access to files like the route matcher, segment parser, or route tree builder in packages/next/src/, which aren't currently in the provided repository data.

Suggestion: Could you ask about specific aspects of App Router routing I can address better, such as how dynamic segments with parameters work, or how nested layouts interact with route resolution?

FOLLOW_UPS:

• How do dynamic segments like [id] work in App Router?
• What's the relationship between layout and page resolution?
• How does App Router handle catch-all routes [...slug]?