score:376

Accepted answer

in the 5.1 release of react-router there is a hook called uselocation, which returns the current location object. this might useful any time you need to know the current url.

import { uselocation } from 'react-router-dom'

function headerview() {
  const location = uselocation();
  console.log(location.pathname);
  return <span>path : {location.pathname}</span>
}

score:1

add

import {withrouter} from 'react-router-dom';

then change your component export

export default withrouter(componentname)

then you can access the route directly within the component itself (without touching anything else in your project) using:

window.location.pathname

tested march 2020 with: "version": "5.1.2"

score:11

i think the author's of react router (v4) just added that withrouter hoc to appease certain users. however, i believe the better approach is to just use render prop and make a simple propsroute component that passes those props. this is easier to test as you it doesn't "connect" the component like withrouter does. have a bunch of nested components wrapped in withrouter and it's not going to be fun. another benefit is you can also use this pass through whatever props you want to the route. here's the simple example using render prop. (pretty much the exact example from their website https://reacttraining.com/react-router/web/api/route/render-func) (src/components/routes/props-route)

import react from 'react';
import { route } from 'react-router';

export const propsroute = ({ component: component, ...props }) => (
  <route
    { ...props }
    render={ renderprops => (<component { ...renderprops } { ...props } />) }
  />
);

export default propsroute;

usage: (notice to get the route params (match.params) you can just use this component and those will be passed for you)

import react from 'react';
import propsroute from 'src/components/routes/props-route';

export const somecomponent = props => (<propsroute component={ profile } />);

also notice that you could pass whatever extra props you want this way too

<propsroute isfetching={ isfetchingprofile } title="user profile" component={ profile } />

score:28

has con posidielov said, the current route is present in this.props.location.pathname.

but if you want to match a more specific field like a key (or a name), you may use matchpath to find the original route reference.

import { matchpath } from `react-router`

const routes = [{
  key: 'page1'
  exact: true,
  path: '/page1/:someparam/',
  component: page1,
},
{
  exact: true,
  key: 'page2',
  path: '/page2',
  component: page2,
},
]

const currentroute = routes.find(
  route => matchpath(this.props.location.pathname, route)
)

console.log(`my current route key is : ${currentroute.key}`)

score:34

here is a solution using history read more

import { createbrowserhistory } from "history";

const history = createbrowserhistory()

inside router

<router>
   {history.location.pathname}
</router>

score:73

there's a hook called uselocation in react-router v5, no need for hoc or other stuff, it's very succinctly and convenient.

import { uselocation } from 'react-router-dom';

const examplecomponent: react.fc = () => {
  const location = uselocation();  

  return (
    <router basename='/app'>
      <main>
        <appbar handlemenuicon={this.handlemenuicon} title={location.pathname} />
      </main>
    </router>
  );
}

score:88

if you are using react's templates, where the end of your react file looks like this: export default somecomponent you need to use the higher-order component (often referred to as an "hoc"), withrouter.

first, you'll need to import withrouter like so:

import {withrouter} from 'react-router-dom';

next, you'll want to use withrouter. you can do this by change your component's export. it's likely you want to change from export default componentname to export default withrouter(componentname).

then you can get the route (and other information) from props. specifically, location, match, and history. the code to spit out the pathname would be: 

console.log(this.props.location.pathname);

a good writeup with additional information is available here: https://reacttraining.com/react-router/core/guides/philosophy

score:246

in react router 4 the current route is in - this.props.location.pathname. just get this.props and verify. if you still do not see location.pathname then you should use the decorator withrouter.

this might look something like this:

import {withrouter} from 'react-router-dom';

const somecomponent = withrouter(props => <mycomponent {...props}/>);

class mycomponent extends react.component {
  somemethod () {
    const {pathname} = this.props.location;
  }
}

Related Query

More Query from same tag