Will gatsby move back to react router with new v6?

[kaushalyap]

Will gatsby move to react router v6 which is much lighter than reach router? Since Reach router will only receive bug fixes and react router will be the surviving project.

[email protected] : 2.9 KB
@reach/[email protected] : 6.4 KB
Potential savings : 3.5 KB

[LekoArts]

Thank you for opening this!

We're not sure about it yet but definitely consider it. We'll wait until the merge is done and see how the reach project is doing. We track it in this issue: #15277

So can't give you a definitive answer for now.

We're marking this issue as answered and closing it for now but please feel free to comment here if you would like to continue this discussion. We also recommend heading over to our communities if you have questions that are not bug reports or feature requests. We hope we managed to help and thank you for using Gatsby!

[dvakatsiienko]

Actually, why this issue is closed and didn't get any attention?

React Router 6 will merge Reacth Router into it, so Reach Router is't the good solution as main router for Gatsby.

[medoms]

Hello, any news on this issue??

I am very interested in moving from Create React App (using react router) to Gatsby using client side only stuff at the beginning. Right now I can see Gatsby using reach router... as both libraries will be merged soon, people in my situation are somehow stuck.

Could anyone shed some light about what plans there are regarding client routers?

Thanks for your time¡¡

[eckdanny]

react-router@6 GA'd today. We just did a PoV migration from a CRA impl to gatsby@4, and [email protected] => @reach | static pages was a pain point. If those invariant build errs went away, we and many others could have a very pleasant migration path

[ZevUhuru]

Bumping this, any plans to merge V6?

[LekoArts]

It seems like V6 made a step backwards in accessibility and thus it's not something we should take lightly: https://twitter.com/mmatuzo/status/1456722149260070916

[olliejm]

Are there any updates on this? Seeing as @reach/router is presumably dead now, is it not an eventuality that Gatsby will have to move to a different router?

[dan2k3k4]

Looks like a fork for @reach/router was made:
https://github.com/gatsbyjs/reach-router