Is Implicit Directory-Based Routing (Like Next.js App Router) Possible?

[Lqm1]

Is it possible to implement implicit directory-based routing similar to Next.js (App Router)?

For example, in Next.js, page routes directly correspond to the directory structure. This is very intuitive and closely resembles how traditional websites are built without using a framework.

• To create /users, you place /users/page.tsx
• To create /users/${userId}, you place /users/${userId}/page.tsx

This mechanism feels natural and easy to understand because it mirrors conventional website structures.

However, TanStack Start currently only supports file-based routing. Even with file-based routing, routes must be explicitly defined per file, and developers need to manually specify which component is rendered for each route.

What I am looking for is a routing system where routes are implicitly tied to directories, and the default exported component from that directory is rendered automatically. In other words, a more intuitive, directory-driven routing approach that does not require explicit route definitions for each page.

[schiller-manuel]

default exported component from that directory is rendered automatically.

very unlikely to happen.

the other thing can probably be implemented via a custom virtual file route based crawler