How does the App Router resolve a URL to a page component?

I can see that [packages/next/src/api/navigation.ts:L1-L2] re-exports from ../client/components/navigation, but I don't have the actual implementation details in the retrieved data. Unfortunately, the repository data provided doesn't contain the core App Router URL resolution logic—the snippets are mostly API re-exports, utility bundles, and test files.

To fully answer your question, I would need access to files like:

• packages/next/src/client/components/navigation.ts (which handles routing)
• App Router matcher/resolver implementations
• Route tree/manifest processing code

What I can tell you is that the repository structure shows routing-related code is organized in packages/next/src/client/components/ (per [packages/next/src/api/navigation.ts]), but the specific implementation of URL-to-page resolution isn't in the provided data.

If you'd like a detailed answer, you may want to ask about:

1. How the App Router builds its route tree from the file system
2. How useRouter() performs route matching
3. The manifest format used for route resolution

FOLLOW_UPS:

• How does Next.js build app directory route manifests?
• What is the format of app router route metadata?
• How does useRouter match URLs to app segments?