SingleSPA MFE React Router issue (advise for migration to TanStack Router)
We are encountering issues with React Router and are considering a switch to TanStack Router. The core driver for the migration thoughts is a <Router> inside <Router> error, which feels pretty unavoidable in our SingleSPA, React 19 Micro-Frontend setup with components being exported from one MFE app and used in other MFE apps. The fact that the component is exported from a JS file that also has the lifecycle functions required for the main MFE app trips up React Router 7 and starts throwing an exception.
Now, before we hop onto the migration train, does TanStack Router have similar restrictions, such as non-nestable BrowserRouter wrappers, or is it expected to work well with each MFE having its own inner routing and singleSPA orchestrating the MFE's main routes that determine when the mount and unmount of these apps occur? Does anyone have any experience with SingleSpa and TanStack Router that could share some tips?
Now, before we hop onto the migration train, does TanStack Router have similar restrictions, such as non-nestable BrowserRouter wrappers, or is it expected to work well with each MFE having its own inner routing and singleSPA orchestrating the MFE's main routes that determine when the mount and unmount of these apps occur? Does anyone have any experience with SingleSpa and TanStack Router that could share some tips?
