[citrusx]

Personally, I can't go with this advice. We're on 2.5 years rolling our own, and it's been really clear that we made the right choice in not going with next.js, which was the only such framework at the time.

Given that the remix author complete broke react-router for our use case (to the point where we can't upgrade to v6), I wouldn't trust that remix could meet our needs, either.

(There is a temptation to fork react-router v5 and maintain it independently. But, we're good just pinning the version for now.)

[brokenbyclouds]

What was it about v6 that made upgrading not feasible? Curious about your use case if you can talk about it more.

[citrusx]

We rely heavily on Redirect components, to support a "legacy" URL structure being forwarded to the current URLs. We are able to resolve these forwards server side during SSR. That whole feature was ripped out, with the suggestion that everyone just use the history API to redirect users, or write a whole bunch of separate controller logic in the server process. This, of course, was not a suitable substitute. When we looked at the "compatibility" plugin to help v5 users migrate to v6, they didn't include this feature in it at all.

https://gist.github.com/mjackson/b5748add2795ce7448a366ae8f8...

Philosophically, he just decided that there was no value to a Redirect component.