A Simple Guide To React Router Sub Routes Setup

Are you building a single-page application with React?

If so, you’ve probably come across the concept of React Router sub routes. This feature helps you organize your app by breaking it down into smaller sections. Not only does it keep your code neat, but it also makes sure your URL matches the current state of your app.

In this article, we’ll explore how React Router sub routes work and how to use them in your projects. We’ll walk through examples and include a helpful diagram to show you the routing structure. By the end, you’ll know exactly how to add and manage sub routes in your React app!

Setting Up React Router in Your Project

Before diving into sub routes and nesting, you need to set up React Router in your project. With the release of React Router v6, things have become even more streamlined and powerful. If you haven’t already installed React Router, you can do so using npm or yarn:

1npm install react-router-dom

Or with yarn:

1yarn add react-router-dom

Once installed, you’ll typically start by wrapping your application in the <BrowserRouter> component. This component enables the use of the HTML5 history API to keep your UI in sync with the URL.

Below is a simple setup in your main entry file (e.g., index.js):

1import React from 'react';
2import ReactDOM from 'react-dom';
3import { BrowserRouter } from 'react-router-dom';
4import App from './App';
5
6ReactDOM.render(
7  <BrowserRouter>
8    <App />
9  </BrowserRouter>,
10  document.getElementById('root')
11);

This basic setup is the foundation on which you can start building a complex routing architecture that includes sub routes and nested routes.

Creating Sub Routes with React Router

Sub routes allow you to define paths that are relative to a parent route. This can be particularly useful when you have multiple sections in your application that share a common layout or require a shared context.

For example, consider an application with a user dashboard. The dashboard might have sub sections like Profile, Settings, and Notifications. Instead of defining separate routes for each section at the top level, you can nest these sub routes under a single dashboard route.

Here’s an example using React Router v6:

1import React from 'react';
2import { Routes, Route, Outlet, Link } from 'react-router-dom';
3
4const Dashboard = () => {
5  return (
6    <div>
7      <h2>Dashboard</h2>
8      <nav>
9        <Link to="profile">Profile</Link> |{' '}
10        <Link to="settings">Settings</Link> |{' '}
11        <Link to="notifications">Notifications</Link>
12      </nav>
13      <Outlet />
14    </div>
15  );
16};
17
18const Profile = () => <h3>User Profile</h3>;
19const Settings = () => <h3>Account Settings</h3>;
20const Notifications = () => <h3>Notifications</h3>;
21
22const App = () => {
23  return (
24    <Routes>
25      <Route path="/" element={<h1>Welcome to the App</h1>} />
26      <Route path="dashboard" element={<Dashboard />}>
27        <Route path="profile" element={<Profile />} />
28        <Route path="settings" element={<Settings />} />
29        <Route path="notifications" element={<Notifications />} />
30      </Route>
31    </Routes>
32  );
33};
34
35export default App;

In this code, the <Outlet /> component in the Dashboard component acts as a placeholder for the nested routes. When the user navigates to /dashboard/profile, the Profile component is rendered inside the Dashboard layout. This structure not only makes your routes more organized but also allows you to share common components and logic across related pages.

Nesting Routes for Better Organization

Nesting routes in React Router is a natural extension of sub routes. It helps to keep your code organized, especially as your application grows. By grouping related routes, you can manage complex navigation scenarios with ease.

Imagine an e-commerce application. You might have a main route for products, and under that, you could nest routes for product details, reviews, and similar products. This hierarchical approach makes it easier to maintain and understand the navigation flow.

Consider the following example:

1import React from 'react';
2import { Routes, Route, Outlet, Link } from 'react-router-dom';
3
4const Products = () => {
5  return (
6    <div>
7      <h2>Products</h2>
8      <nav>
9        <Link to="details">Details</Link> |{' '}
10        <Link to="reviews">Reviews</Link> |{' '}
11        <Link to="similar">Similar Products</Link>
12      </nav>
13      <Outlet />
14    </div>
15  );
16};
17
18const Details = () => <div><h3>Product Details</h3><p>Information about the product.</p></div>;
19const Reviews = () => <div><h3>Product Reviews</h3><p>Customer reviews.</p></div>;
20const SimilarProducts = () => <div><h3>Similar Products</h3><p>List of similar items.</p></div>;
21
22const App = () => {
23  return (
24    <Routes>
25      <Route path="/" element={<h1>Home</h1>} />
26      <Route path="products" element={<Products />}>
27        <Route path="details" element={<Details />} />
28        <Route path="reviews" element={<Reviews />} />
29        <Route path="similar" element={<SimilarProducts />} />
30      </Route>
31    </Routes>
32  );
33};
34
35export default App;

Here, the <Products /> component serves as the parent route. Its children—Details, Reviews, and SimilarProducts—are nested inside it. This hierarchical structure is particularly useful for applying shared logic, layouts, or state across all nested routes.

Implementing Dynamic Sub Routes in a React App

Dynamic routing is another critical feature in modern web applications. With React Router, you can define routes that include dynamic segments. This is especially useful when dealing with data-driven applications, where the content displayed is based on the parameters passed in the URL.

For example, consider a blog application where each post has a unique ID. You can set up a dynamic route like so:

1import React from 'react';
2import { Routes, Route, Outlet, useParams, Link } from 'react-router-dom';
3
4const Blog = () => {
5  return (
6    <div>
7      <h2>Blog</h2>
8      <nav>
9        <Link to="post/1">Post 1</Link> |{' '}
10        <Link to="post/2">Post 2</Link> |{' '}
11        <Link to="post/3">Post 3</Link>
12      </nav>
13      <Outlet />
14    </div>
15  );
16};
17
18const Post = () => {
19  const { postId } = useParams();
20  return (
21    <div>
22      <h3>Post {postId}</h3>
23      <p>This is the detail page for post {postId}.</p>
24    </div>
25  );
26};
27
28const App = () => {
29  return (
30    <Routes>
31      <Route path="/" element={<h1>Home</h1>} />
32      <Route path="blog" element={<Blog />}>
33        <Route path="post/:postId" element={<Post />} />
34      </Route>
35    </Routes>
36  );
37};
38
39export default App;

In this example, the :postId parameter in the route path allows the Post component to capture dynamic segments from the URL. This enables your application to render different content based on the URL parameter, which is a powerful feature for creating dynamic, data-driven web applications.

Integrating a Diagram to Visualize Routing

Understanding complex routing structures can be challenging. Visual aids, such as diagrams, can help you grasp the hierarchical nature of nested routes and sub routes. The diagram below illustrates how routes can be organized in a React application:

1graph TD
2    A[App] --> B[Home]
3    A --> C[Dashboard]
4    C --> D[Profile]
5    C --> E[Settings]
6    C --> F[Notifications]
7    A --> G[Products]
8    G --> H[Details]
9    G --> I[Reviews]
10    G --> J[Similar Products]
11    A --> K[Blog]
12    K --> L[Post/:postId]

This visual representation shows the main application route (App) branching into several primary routes like Home, Dashboard, Products, and Blog. Each of these routes further divides into sub routes (e.g., Dashboard has Profile, Settings, and Notifications). Such a diagram helps in planning and debugging the routing structure, ensuring that each nested route is correctly configured.

Advanced Techniques for Nested Routing

Beyond the basics, there are several advanced techniques that can enhance your routing strategy in React. These include:

Index Routes

Sometimes, you might want to render a default child component when no sub route is provided. React Router supports index routes to handle this scenario.

1import React from 'react';
2import { Routes, Route, Outlet, Link } from 'react-router-dom';
3
4const Dashboard = () => (
5  <div>
6    <h2>Dashboard</h2>
7    <nav>
8      <Link to="profile">Profile</Link> |{' '}
9      <Link to="settings">Settings</Link>
10    </nav>
11    <Outlet />
12  </div>
13);
14
15const IndexDashboard = () => <h3>Welcome to your Dashboard</h3>;
16
17const App = () => (
18  <Routes>
19    <Route path="/" element={<h1>Home</h1>} />
20    <Route path="dashboard" element={<Dashboard />}>
21      <Route index element={<IndexDashboard />} />
22      <Route path="profile" element={<div><h3>Profile</h3></div>} />
23      <Route path="settings" element={<div><h3>Settings</h3></div>} />
24    </Route>
25  </Routes>
26);
27
28export default App;

Route Guards

You may want to restrict access to certain routes based on user authentication or roles. Implementing route guards can be achieved by wrapping your route components in higher-order components (HOCs) or using custom hooks that validate user permissions before rendering the component.

Lazy Loading Routes

For larger applications, lazy loading components can improve performance by splitting your code and loading components only when they are needed. React Router supports lazy loading through React.lazy and Suspense.

1import React, { Suspense, lazy } from 'react';
2import { Routes, Route } from 'react-router-dom';
3
4const Dashboard = lazy(() => import('./Dashboard'));
5const Profile = lazy(() => import('./Profile'));
6const Settings = lazy(() => import('./Settings'));
7
8const App = () => (
9  <Suspense fallback={<div>Loading...</div>}>
10    <Routes>
11      <Route path="/" element={<h1>Home</h1>} />
12      <Route path="dashboard" element={<Dashboard />}>
13        <Route path="profile" element={<Profile />} />
14        <Route path="settings" element={<Settings />} />
15      </Route>
16    </Routes>
17  </Suspense>
18);
19
20export default App;

These techniques, when combined, allow you to build highly scalable and efficient React applications with complex routing requirements.

Best Practices and Common Pitfalls

When working with React Router sub routes and nested routing, there are several best practices to follow:

• Keep Routes Organized:
  Structure your route definitions in a way that mirrors your component hierarchy. This makes it easier to manage and debug your routes.

• Use the Outlet Component:
  Always use the <Outlet /> component to render nested routes. This keeps your layout consistent and ensures that your nested components receive the correct context.

• Handle Non-Existent Routes:
  Always include a fallback route (e.g., a 404 Not Found page) for unmatched routes. This enhances the user experience and prevents confusion.

• Mind the Order of Routes:
  Ensure that your route definitions do not conflict with one another. More specific routes should be defined before generic ones to avoid unexpected behavior.

• Test Your Routes Thoroughly:
  As your routing logic becomes more complex, it is vital to write tests to ensure that your routes behave as expected. Tools like Jest and React Testing Library can be very helpful in this regard.

Common pitfalls include:

• Incorrect nesting: Not using <Outlet /> properly can lead to routes not rendering as expected.

• Overcomplicating routing logic: Keep your routing logic as simple as possible. Refactor complex routes into smaller, more manageable components.

• Ignoring URL parameters: When using dynamic segments, always validate and sanitize URL parameters to avoid potential security risks.

Wrapping Up React Router Sub Routes

Using React Router sub routes in your application can simplify routing and make it more organized. By setting up nested routes properly, you create an easy-to-manage and scalable structure. With these practices, you can handle complex applications with ease. Start applying the concepts from this article and see how React Router sub routes improve your project’s modularity and maintainability.

To summarize:

• Sub routes help you manage sections of your application efficiently.
• Nesting routes offers a clear, hierarchical structure that mirrors your component layout.
• Dynamic routes empower your application to handle data-driven content.
• Advanced techniques such as index routes, lazy loading, and route guards further optimize your routing strategy.

As you continue to build more complex applications, consider exploring additional React Router features and integrating state management solutions to handle route-based data fetching and authentication. The journey towards mastering routing in React is ongoing, and staying updated with the latest best practices and library updates will ensure your application remains robust and user-friendly.

Short on time? Speed things up with DhiWise!

Tired of manually designing screens, coding on weekends, and technical debt? Let DhiWise handle it for you!

You can build an e-commerce store, healthcare app, portfolio, blogging website, social media or admin panel right away. Use our library of 40+ pre-built free templates to create your first application using DhiWise.