React uses Router to get the current route
Use useLocation()
the hook to get the current route through React Router, for example const location = useLocation()
. The hook returns the current location object. For example, we can access the pathname as location.pathname.
import React from 'react';
import {Route, Link, Routes, useLocation} from 'react-router-dom';
export default function App() {
const location = useLocation();
console.log('hash', location.hash);
console.log('pathname', location.pathname);
console.log('search', location.search);
return (
<div>
<div>
<h2>Current Pathname 👉️ {location.pathname}</h2>
<h2>Current Search params 👉️ {location.search}</h2>
<h2>Current Hash 👉️ {location.hash}</h2>
<nav>
<ul>
<li>
<Link to="/">Home</Link>
</li>
<li>
<Link to="/about">About</Link>
</li>
<li>
<Link to="/users?page=10">Users</Link>
</li>
<li>
<Link to="/users?page=10#myHash">Users with hash</Link>
</li>
</ul>
</nav>
<Routes>
<Route path="/about" element={<About />} />
<Route path="/" element={<Home />} />
</Routes>
</div>
</div>
);
}
function Home() {
return <h2>Home</h2>;
}
function About() {
return <h2>About</h2>;
}
We use the useLocation hook to get the current location object.
Some of the properties that can be accessed on the location object are:
- pathname - the current pathname, e.g. /Users
- search - the current query string, e.g. ?page=10
-
hash - the current hash value,
#example
e.g.
When using react router hooks, make sure to wrap our application in a router component in the index.js file.
index.js
import {createRoot} from 'react-dom/client'; import App from './App'; import {BrowserRouter as Router} from 'react-router-dom'; const rootElement = document.getElementById('root'); const root = createRoot(rootElement); // wrap App in Router root.render( <Router> <App /> </Router> );
The best place to wrap your React application with the Router component is in the index.js file, since this is the entry point for your React application.
Once your entire app is wrapped in a Router component, you can use any hook from the react router package anywhere in your component.
If you have dynamic routes and try to access their IDs, use useParams
the hook.
import React from 'react';
import {Route, Link, Routes, useParams} from 'react-router-dom';
function Users() {
// get ID from url
const params = useParams();
console.log(params); // {userId: '12345'}
return <h2>userId is 👉️ {params.userId}</h2>;
}
export default function App() {
return (
<div>
<div>
<nav>
<ul>
<li>
<Link to="/">Home</Link>
</li>
<li>
<Link to="/about">About</Link>
</li>
<li>
{/* link to dynamic path */}
<Link to="/users/12345">Users</Link>
</li>
</ul>
</nav>
<Routes>
<Route path="/about" element={<About />} />
{/* handle dynamic path */}
<Route path="/users/:userId" element={<Users />} />
<Route path="/" element={<Home />} />
</Routes>
</div>
</div>
);
}
function Home() {
return <h2>Home</h2>;
}
function About() {
return <h2>About</h2>;
}
The useParams hook returns <Route path>
an object of key-value pairs of dynamic parameters matching the current URL.
Notice that we set a dynamic path property - on the Route component that renders the User component <Route path="/users/:userId" element={<Users />} />
.
When visiting /users/some-id , we can use the useParams hook to get the ID.
function Users() {
// get ID from url
const params = useParams();
console.log(params); // 👉️ {userId: '12345'}
return <h2>userId is 👉️ {params.userId}</h2>;
}
This route will match anything after /users/, such as /users/123 or /users/asdf .
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Fix Uncaught ReferenceError: useState is not defined in React
Publish Date:2025/03/15 Views:142 Category:React
-
When we use the useState hook in our code but forget to import it, it generates the error Uncaught ReferenceError: useState is not defined. To fix this error, you need to import the hook before using it import {useState} from react . // ?️
React error Uncaught ReferenceError: process is not defined solution
Publish Date:2025/03/15 Views:116 Category:React
-
要解决 React 中的“Uncaught ReferenceError: process is not defined” 错误,需要在项目的根目录中打开终端并通过运行 `npm install react-scripts@latest` 更新 `react-scripts` 包的版本,并在必要时重新安装
How to solve the "Function components cannot have string refs" error in React
Publish Date:2025/03/15 Views:138 Category:React
-
当我们在函数组件中使用字符串作为引用时,会出现错误“Function components cannot have string refs”。 要解决该错误,需要使用 useRef() 钩子来获取一个可变的 ref 对象,我们可以将其用作组件
React Error Property 'X' does not exist on type 'Readonly<{}>'
Publish Date:2025/03/15 Views:139 Category:React
-
当我们尝试访问未键入的类组件的 props 或状态时,会发生 React.js 错误“Property does not exist on type 'Readonly '”。 要解决该错误,需要使用 React.Component 类上的泛型来输入该类的道具或状
Solve React's Unexpected default export of anonymous function error
Publish Date:2025/03/15 Views:119 Category:React
-
当我们尝试使用默认导出导出匿名函数时,会导致“Unexpected default export of anonymous function”警告。 要解决此错误,需要在导出函数之前为其命名。
React error Type '() => JSX.Element[]' is not assignable to type FunctionCompo
Publish Date:2025/03/15 Views:51 Category:React
-
当我们尝试从函数组件返回元素数组时,会发生 React.js 错误“Type '() => JSX.Element[]' is not assignable to type FunctionComponent”。 要解决该错误,需要将元素数组包装到 React 片段中。
How to solve React Type {children: Element} has no properties in common with type
Publish Date:2025/03/15 Views:103 Category:React
-
React.js 错误“Type {children: Element} has no properties in common with type IntrinsicAttributes” 当我们尝试将 children 道具传递给不带任何道具的组件时发生。 要解决错误,需要定义并键入组件上的属性
Fix the value prop on input should not be null error in React
Publish Date:2025/03/15 Views:141 Category:React
-
当我们将输入的初始值设置为 null 或覆盖将其设置为 null 的初始值时,会导致警告“value prop on input should not be null”,例如 来自空的 API 响应。 使用后备值来解决这个问题。
Property does not exist on type 'JSX.IntrinsicElements' error in React
Publish Date:2025/03/15 Views:188 Category:React
-
当组件的名称以小写字母开头时,会出现错误“Property does not exist on type 'JSX.IntrinsicElements”。 要解决该错误,需要确保始终以大写字母开头组件名称,安装 React 类型并重新启动我们的开