React Router v4 <NavLink> vs <Link> benefits

reactjs react-router react-router-v4
yam55 picture yam55 · Nov 16, 2017 · Viewed 71.8k times · Source

Besides the ability to set an "activeClassName" and "activeStyle" on NavLink, is there any reason to use NavLink over Link when creating links to other routes on non-navigational elements (ie. not main nav in header or footer) on your site that don't need an active state/class?

Answer

Abdennour TOUMI picture Abdennour TOUMI · Nov 16, 2017

The official documentation is clear:

<NavLink>

A special version of the <Link> that will add styling attributes to the rendered element when it matches the current URL.

Thus, the answer is NO. There are no other reasons except the mentioned one.

Related questions

How to push to History in React Router v4?

In the current version of React Router (v3) I can accept a server response and use browserHistory.push to go to the appropriate response page. However, this isn't available in v4, and I'm not sure what the appropriate way to …

Read More
React Router v4 - How to get current route?

I'd like to display a title in <AppBar /> that is somehow passed in from the current route. In React Router v4, how would <AppBar /> be able to get the current route passed into it's title prop? &…

Read More
Nested routes with react router v4 / v5

I am currently struggling with nesting routes using react router v4. The closest example was the route config in the React-Router v4 Documentation. I want to split my app in 2 different parts. A frontend and an admin area. I was …

Read More