Inconsistent basename behavior between Components and Middleware in Framework Mode

[KimotoYanke]

Hi.

My team is developing a project using Framework mode with a basename configured in the URL. We're running into an issue where basename is handled inconsistently depending on context.

Reproduction repository: https://github.com/KimotoYanke/react-router-basename-test (basename is set to /base/)

Current Behavior

In components, basename is handled automatically and transparently. For example, a <Link> or navigate() call targeting the login page can be written simply as /login, and React Router correctly resolves it to /base/login.

However, in middleware, throw redirect("/login") does not apply the basename — it redirects to /login instead of /base/login, resulting in a not-found error. As a workaround, we have to write throw redirect(joinURL(import.meta.env.BASE_URL, "login"))

Questions

1. Is this the intended behavior? In other words, is it by design that middleware does not automatically prepend basename to redirect paths?
2. Is there any plan to make middleware behavior consistent with component behavior regarding basename handling?

I'd appreciate any clarification. Thank you!

[aniruddhaadak80]

@KimotoYanke Your observation is reasonable: basename-aware URL generation in components and explicit middleware redirects are not always symmetrical by default.

A practical pattern is to centralize redirect URL creation (for example a helper that prefixes import.meta.env.BASE_URL), and use that helper consistently in middleware. That avoids drift between component routing and middleware behavior.

So yes, your workaround style is generally the right defensive approach until middleware basename behavior is unified.

Sources:

• https://reactrouter.com/start/framework/routing
• https://reactrouter.com/api/utils/redirect