Lazy-loaded nested routes not rendering after redirect from login (Outlet stays empty)

[suzuki-shm]

Background

I'm building an app using React Router v7 with the following route file structure:

routes/
├── _app._index.tsx
├── _app.foo.$bar.tsx 
├── _app.foo.tsx 
├── _app.tsx
├── login.tsx
├── logout.tsx

The app behavior is intended as follows:

1. When visiting /, the loader checks for session info.
2. If no session is found, it redirects to /login.
3. After a successful login, the user is redirected back to /.
4. At that point, _app.tsx should render the sidebar, and _app._index.tsx should render the page content.

Problem

However, after redirecting from /login to /, the page renders a blank screen.
No error appears in the console, and on manual reload (with session present), the app loads correctly.

Research

I added console logs and verified that:

• The loaders for root.tsx, _app.tsx, and _app._index.tsx are called.
• The root.tsx component itself is rendered.
• But the Outlet inside root.tsx does not render any child content after the redirect.

After some investigation, I found that setting routeDiscovery: { mode: "initial" } in react-router.config.ts (thus disabling lazy route discovery) causes everything to render correctly — the redirect works, and the content loads as expected.

My understanding is that lazy route discovery is meant to reduce bandwidth usage by deferring loading of nested routes until needed. I'd like to preserve this behavior. However, I couldn't find clear documentation about how the __manifest system interacts with lazy route discovery.

Additionally, to investigate the behavior of __manifest endpoint, I observed the loading behavior during the following steps:

1. Accessing / while not logged in: no fetching to __manifest

2. Being redirected to /login: Fetch to http://localhost:3000/credit/__manifest?p=%2FMY_APP_NAME%2Flogin&version=...

{"root":{"id":"root","path":"","module":"/MY_APP_NAME/app/root.tsx","hasAction":false,"hasLoader":false,"hasClientAction":false,"hasClientLoader":false,"hasClientMiddleware":false,"hasErrorBoundary":false,"imports":[]},"routes/login":{"id":"routes/login","parentId":"root","path":"login","module":"/MY_APP_NAME/app/routes/login.tsx","hasAction":true,"hasLoader":true,"hasClientAction":false,"hasClientLoader":false,"hasClientMiddleware":false,"hasErrorBoundary":false,"imports":[]}}

3. Redirecting back to / after login: no fetching to __manifest

Questions:

What would be the recommended way to make Lazy Route Discovery work correctly with this kind of route structure and redirect flow?

Any guidance would be greatly appreciated.
Thanks!

Related Issues

• RR7 lazyRouteDiscover (Fog of War) opt-out #12656
• [Docs] Explanation: Lazy Route Discovery #12826

---

Version info

• React Router: 7.6
• React Version: 18.3.1
• vite: 5.4.19