You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our plan is to move back to react-router however we'll first need to make sure that it's as accessible as the current @reach/router we use. Furthermore, there might be some breaking changes so we're tracking this really here: #15277 (This is not an umbrella issue)
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!
Summary
Considering React Router is deciding to double down on RR instead of Reach, will Gatsby be integrating now?
Relevant information
https://reacttraining.com/blog/reach-react-router-future/
Environment (if relevant)
File contents (if changed)
gatsby-config.js
: N/Apackage.json
: N/Agatsby-node.js
: N/Agatsby-browser.js
: N/Agatsby-ssr.js
: N/AThe text was updated successfully, but these errors were encountered: