Javascript
React Router
React.js
React Router is a JS library available through NPM that helps mainly with 2 problems:
This is how you would install React Router in your project:
1$ npm install --save react-router
Stop reading if you are not building entire applications using React, you don’t need React-Router for single-page applications or small components.
For the rest of us building real web applications, we need to connect several views (React components) into one big application. That process is called "routing."
For example, we need the following application URLs to match the following components:
What pages/views do you want your app to have? You can always start with the basic ones:
The rest of the pages depend on your application and on how you want your users to navigate through your site.
This is the sitemap for any typical e-commerce website:
Once you have finished mapping your application views with URLs, you can start coding everything, and that is when React-Router comes in!
The best practice is always to create one component called <Layout />
which will take care of routing the users to the specific views they should see, depending on each of the particular URLs.
This is an example of the same e-commerce sitemap but now using React Router v6:
1// This component <Layout /> will take care of routing the URLs with all my application views 2 3export const Layout = () => { 4 return ( 5 <div> 6 <BrowserRouter> 7 <Routes> 8 <Route element={<Home />} path="/" /> 9 <Route element={<Demo />} path="/demo" /> 10 <Route element={<Single />} path="/single/:theid" /> 11 <Route element={<h1>Not found!</h1>} /> 12 </Routes> 13 </BrowserRouter> 14 </div> 15 ); 16}
There are 3 components to understand here:
<BrowserRouter>
: Every time you open a new BrowserRouter tag, you are basically telling React that everything that is inside must be conditionally rendered, based on particular <Routes>
: Works similar to the switch statement in JavaScript but for Routes... It tells React that only the first <Route>
that matches the URL will be displayed.<Route>
: It’s the way of React-Router to map routes with components, for example:1<Route element={<Signup />} path="/sign-up" />
This route is telling React that when the URL matches "sign-up", the component Signup should be displayed.
<a>
are now a ProblemAnchors take users to other websites or URLs, and that is amazing for simple plain HTML+JS, but now we DON’T want our users to be taken to other websites or URLs. We want them to remain in the same tab but be able to load the next page without having to refresh. We have two possible approaches of doing that:
<Link>
tag:React Router created a component that we can use instead of <a>
:
1<Link to="/login">Take me to login</Link>
React Router always passes to each view a prop called "history", which contains a lot of useful information to use when routing users. One of its many useful utilities is the "push" function, which basically redirects the user to a given path.
You can access the history object by using the useNavigate
hook like this:
1import { useNavigate } from "react-router-dom"; 2 3// Inside the component, you declare the useNavigate this way: 4const navigate = useNavigate();
Then, anywhere in any of your components, you can programmatically redirect users to another URL like this:
1<button onClick={() => navigate("/login")}>Take me to login</button>
Here is a live example using everything that we've learned in this reading. Please click and play to understand it, learn it and replicate it: