Configurable __manifest route for lazyRouteDiscovery feature

[johannesbraeunig]

Background

We're running multiple Remix applications on a single domain, structured by distinct basePath segments. For example:

• http://remix.run.com/register → Register App
• http://remix.run.com/docs → Docs App

Each app operates independently and can have deeply nested routes, such as:
http://remix.run.com/docs/intro/first/page/ → served by the Docs App.

---

The Issue

After enabling the future flag v3_lazyRouteDiscovery, we encountered a critical problem:

The __manifest route is shared across all apps on the same domain.
This behavior assumes the __manifest route exists at the root level of the domain, causing conflicts and breaking the app where this flag was enabled.

This issue has been previously highlighted by @JLarky: Discussion Comment.

---

Proposed Solution

To resolve this, the destination of the __manifest route should be configurable.
As mentioned by @brophdawg11 in the linked discussion, it seems this functionality may already exist but has not been shipped yet.

By allowing customization of the __manifest route location, Remix applications can operate independently on the same domain without conflict, ensuring compatibility with the lazyRouteDiscovery feature.

---

We’d appreciate feedback on whether this configuration is already available or if there are plans to introduce it soon.

Thank you for your work and support! 🙌

[philippd]

We’ve encountered the same issue and would also like the __manifest route to be configurable.

An even better solution for us, given our relatively small manifest file, would be a configuration option to opt out of lazy route discovery entirely and keep serving a static manifest file instead.