DEV Community

React router V6: Some of the new changes

Gabriel Bittencourt on November 19, 2021

So not too long ago the library React Router has updated to version 6 and with that it came with some interesting changes that I notice and see pe...
Collapse
 
sgarciadev profile image
Sergei Garcia • Edited

Thanks for the article! As for feedback and anyone else reading this, you missed a lot of the more important, key, breaking changes React Router v6 introduced which you might want to double check. I think you focused a little too much on some of the less important ones (like NavLink's className prop)

  • The <Route> component has now deprecated its children & render props, so it's no longer possible to pass router props like history / location / match to components. You should now use the useNavigate / useLocation / useParams hooks.
  • The withRouter Higher Order Component which made it possible to get router props anywhere has also been deprecated in favor of React Hooks
  • The new <Routes> component that replaces <Switch> works entirely different now. It now will always focus on matching the most specific route instead of the first one it finds, making it more predictable.
  • Relative links work dramatically better and more predictably now.
  • Route patterns using Regexp are now deprecated, the only supported symbols are now : for dynamic routes (user/:id) and the * wildcard which can only be used at the end.

For anyone else curious to learn more about these v6 changes (and the reason behind them), I would strongly discourage any kind of video material such as the one linked from Academind linked, and instead recommend the official React Router v6 announcement blog post which does an incredibly great job explaining all the changes in a well explained, yet concise manner. As well as the reasons that drove the team to make them.

Collapse
 
rinsarmu profile image
Robera Insarmu

very well noted

Collapse
 
atefehpahlevan2020 profile image
Atefeh Pahlevan

Thanks for the post you made about the difference between version 5 and 6. I hope you are always successful.

Collapse
 
not4ro profile image
Matteo Notaro

I'm trying it but there's one thing that hurts me...
I'm from Angular and i've noticed that you have to declare in one single place ALL the possible routes of the app (for nested routing you have to declare them inside a Route like this


<Route path={"father"} element={Father}>
<Route path={"child"} element={Child}/>
</Route>

It is possible to have a more "clean" way to declare the sub-path in the father component?

Collapse
 
gabrlcj profile image
Gabriel Bittencourt • Edited

So you can attach at the end of the path of your father component a "/*", so react router will know that this route will only show if it starts with that path name and not the exact path name like this

<Routes>
  <Route path="/welcome/*" component={<Father />} />
</Routes>
Enter fullscreen mode Exit fullscreen mode

And then have other paths starting with the same path name but with some additional name at the end, so inside the father component you have it's child component and there you can put the nested route for that specific path name to render the child component like this

<Routes>
  <Route path="new-user" component={<Child />} />
</Routes>
Enter fullscreen mode Exit fullscreen mode

So you don't have to put all the routes in to the same file, and if they're nested routes you can just add the "/*" at the end of that path name and create a route inside the child component, so it loads when it match's the URL.

Collapse
 
not4ro profile image
Matteo Notaro

God bless you, ty

Collapse
 
urielbitton profile image
Uriel Bitton

ugh...please don't surround string values with curly braces!
Bad: path={"/father"}
Good: path="/father"

Collapse
 
miionu profile image
Rospars Quentin

I like the new Routes component instead of Switch, helps a lot to clarify the code :)

Collapse
 
gabrlcj profile image
Gabriel Bittencourt

Yeah me too, a much better understanding of the code!

Collapse
 
kona profile image
Bara Konateh

Yeah definitely helps with the readability, although I think switch made sense. Not a big fan of the activeClassName prop change though

Collapse
 
aliezeali profile image
Alieze-Ali

Great article, thanks!

Collapse
 
gabrlcj profile image
Gabriel Bittencourt

I'm glad you like it!!

Collapse
 
napster profile image
Marouane Etaraz

Thank you

Collapse
 
sm3dev profile image
Michael P. Wright, SM₃

Thanks for this and the links! πŸ™πŸΎπŸ™πŸΎ

Collapse
 
gabrlcj profile image
Gabriel Bittencourt

I'm glad you find useful!!!

Collapse
 
mridulbagla profile image
Mridul Bagla

Thanks :-)

Some comments have been hidden by the post's author - find out more