Replies: 2 comments
-
If there are no solutions to this we could have {
// others
externalRoutes: ["../app1/routes", "../app2/routes"]
} |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm also experiencing the same problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In our monorepo we have:
Each of these is a TanStack Router app using file-based routing. We could build
app1
,app2
andapp3
separately, host them as three different processes, and use a complex network (or Kubernetes) config to route them under one origin:I’d like to replace that with a single “container” app that dynamically loads and mounts all three, but still preserves auto-code-splitting. My current approach is:
This lets us build only the container—but unfortunately it bundles everything into one huge file and loses the automatic splitting. Are there any recommended approaches this?
Beta Was this translation helpful? Give feedback.
All reactions