How to set different route.tsx to pathless routes?

[chanidog]

I have 2 pathless routes: _app and _admin. Both has <Outlet /> so they serve as layouts which is at the top-level of routes/ dir so when i generate the routes they conflict:

$ tsr generate ⊘ cache disabled
Error: Conflicting configuration paths were found for the following routes: "/route", "/route".
Please ensure each Route has a unique full path.
Conflicting files: 
 /home/chani/Projects/lemie-lms/src/routes/_admin/route.tsx
 /home/chani/Projects/lemie-lms/src/routes/_app/route.tsx

I would like different routes for each of those groups so that i can have different layouts for all of the routes on each group similar to in nextjs

[latent-9]

The conflict isn't coming from the route.tsx naming. That part is correct: _app/route.tsx and _admin/route.tsx are the right way to define the route file for a directory. The problem is that _app and _admin are pathless layout routes (the _ prefix means "don't contribute a URL segment"), and right now they're empty: each one only renders <Outlet /> with no child routes underneath. A pathless layout with no children has no URL path of its own, so both _app and _admin resolve to the exact same full path, and the generator refuses because two routes can't own the same path.

Pathless layout routes aren't standalone pages; they exist purely to wrap child routes. As soon as you put actual routes inside each group, the collision disappears and each group gets its own layout, which is exactly the Next.js route-group behavior you're after:

src/routes/
├── __root.tsx
├── _app/
│   ├── route.tsx        // layout for the "app" group  (<Outlet/>)
│   ├── dashboard.tsx    // -> /dashboard   (rendered inside _app)
│   └── profile.tsx      // -> /profile     (rendered inside _app)
└── _admin/
    ├── route.tsx        // layout for the "admin" group (<Outlet/>)
    ├── users.tsx        // -> /users       (rendered inside _admin)
    └── settings.tsx     // -> /settings    (rendered inside _admin)

tsr generate now succeeds, and the generated tree nests each child under its own pathless layout:

/_app     (path '')   -> /_app/dashboard (/dashboard), /_app/profile (/profile)
/_admin   (path '')   -> /_admin/users (/users),       /_admin/settings (/settings)

So every file inside _app/ uses the _app/route.tsx layout and every file inside _admin/ uses the _admin/route.tsx layout. Two independent layout trees, no URL segment added, just like Next.js route groups.

Two things worth noting:

• The one rule you can't break is that a concrete path can only belong to one route. If you put an index.tsx in both groups, both would resolve to / and you'd get the same conflict back, since only one group can own a given path.
• Renaming the route token to layout (as suggested above) is purely cosmetic; it makes route.tsx become layout.tsx, but empty pathless layouts would still collide the same way. The fix is giving each group its child routes, not renaming the token.

Docs: Pathless Layout Routes and File Naming Conventions.