React Router 5 was easy to refer. I am moving away from React Router 6 as the data fetching pattern is not aligned with how I design my components.
These days, I am leaning toward Tanstack Router. Still, it seems like the codebase has not stabilized yet to minimize breaking changes (not a personal experience but based on comments from other developers).
I use React Router 6 with Components. I guess @rjdavid you were not satisfied with the way it moved towards hooks. I think the Components part in 5 and 6 are similar.
Whatever @rjdavid … you could do more with that attitude but that is up to you.
From V5 to V6.4 if you use the “old” way existing in 5 (no hooks or data API) nothing is changing. Thus my supposition that you adopted the data API and/or hooks.
React Router 6.4 has a new data pattern that is unavailable from the previous versions.
React Router’s data fetching pattern moves data loading on the navigation (route). I understand why they want to do this, and the benefits are clear. UX, simpler SSR, etc.
The disadvantage is that following this pattern means that components down the component tree must move the data fetching up to the route (and maybe use context to get the data down the component tree). Worse DX, difficult component sharing, etc.
Personally, I want my data fetching done near the component that used the data.
I haven’t delved into the new approach yet, so I’m wondering if it is not possible to do both?
Load data that are used through multiple pages up on the router and smaller data sets near their components?
We need to fix up our guide. A lot of it needs to be rewritten.
For React, we suggest using React Router. It’s popular and works well with Meteor. I’m not sure about the new ways to fetch data in version 6, so I might be using old methods.
@storyteller, you are correct. You can indeed do both. Apps running in React Router 6 before 6.4 will still run without problems in 6.4.
I just do not want to invest my limited resources in a tool that will be developed in another direction, as future features and priorities will not be useful to me since the new routers are now the recommended components to be used. A personal preference.
I was on the fence on this because of React 19 RC0 which completely supported this async pattern that React Router 6.4 is pushing. Fortunately for me, React 19 RC1 released a few days ago fixed this:
I will have to do a deep dive into this to see if there is a better way or how we can optimize things for Meteor. I have been growing increasingly unhappy with the speed of loading data in my apps. Not sure if the new way React does things is a solution, but we have to experiment with that.
That said maybe it is time to make Flow Router great again and work with all the front-ends.
