Client-side routing concept in React

Introduction

Client-side routing lets your React app change pages without reloading the whole website. It makes the app feel faster and smoother.

When building a single-page app that shows different views or pages.

When you want users to navigate without waiting for full page reloads.

When you want to keep the app state while switching pages.

When you want to update the browser address bar to match the current view.

When you want to handle navigation inside your React app easily.

Syntax

React

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/about" element={<About />} />
      </Routes>
    </BrowserRouter>
  );
}

BrowserRouter wraps your app to enable routing.

Routes contains all your route definitions.

Route defines a path and which component to show.

Examples

Basic routing with two pages: Home and Contact.

React

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/contact" element={<Contact />} />
      </Routes>
    </BrowserRouter>
  );
}

Route with a dynamic parameter :userId to show different profiles.

React

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/profile/:userId" element={<Profile />} />
      </Routes>
    </BrowserRouter>
  );
}

Redirect from an old path to a new path using Navigate.

React

import { BrowserRouter, Routes, Route, Navigate } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/old-path" element={<Navigate to="/new-path" replace />} />
        <Route path="/new-path" element={<NewPage />} />
      </Routes>
    </BrowserRouter>
  );
}

Sample Program

This React app uses client-side routing to switch between Home and About pages without reloading. The navigation links update the URL and show the correct page content instantly.

React

import React from 'react';
import { BrowserRouter, Routes, Route, Link } from 'react-router-dom';

function Home() {
  return <h2>Home Page</h2>;
}

function About() {
  return <h2>About Page</h2>;
}

export default function App() {
  return (
    <BrowserRouter>
      <nav aria-label="Main navigation">
        <ul>
          <li><Link to="/">Home</Link></li>
          <li><Link to="/about">About</Link></li>
        </ul>
      </nav>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/about" element={<About />} />
      </Routes>
    </BrowserRouter>
  );
}

Important Notes

Client-side routing keeps the app fast by avoiding full page reloads.

Use semantic HTML and ARIA labels for accessible navigation.

Remember to install react-router-dom to use routing features.

Summary

Client-side routing changes views without reloading the page.

Use BrowserRouter, Routes, and Route to set up routes.

Navigation links update the URL and show the right content instantly.

Practice

1. What is the main purpose of client-side routing in a React application?

easy

A. To handle server-side rendering only

B. To reload the whole page when navigating

C. To change views without reloading the entire page

D. To manage database connections

Solution

1. Step 1: Understand client-side routing

   Client-side routing allows changing the visible content without refreshing the whole page, making navigation faster and smoother.

2. Step 2: Compare options

   Options B, C, and D describe behaviors unrelated to client-side routing in React.

3. Final Answer:

   To change views without reloading the entire page -> Option C

4. Quick Check:

   Client-side routing = change views without reload [OK]

Hint: Client-side routing avoids full page reloads [OK]

Common Mistakes:

• Confusing client-side routing with server-side rendering
• Thinking navigation always reloads the page
• Assuming routing manages backend tasks

2. Which of the following is the correct way to import components for client-side routing in React?

easy

A. import { BrowserRouter, Routes, Route } from 'react-router-dom';

B. import { Router, RouteList, Route } from 'react-router';

C. import { BrowserRouter, Route, Link } from 'react-router';

D. import { Router, Routes, Link } from 'react-router-dom';

Solution

1. Step 1: Identify the correct package and components

   The official React routing library is 'react-router-dom' and the main components are BrowserRouter, Routes, and Route.

2. Step 2: Check each import statement

   Only import { BrowserRouter, Routes, Route } from 'react-router-dom'; correctly imports BrowserRouter, Routes, and Route from 'react-router-dom'. Others use incorrect component names or wrong packages.

3. Final Answer:

   import { BrowserRouter, Routes, Route } from 'react-router-dom'; -> Option A

4. Quick Check:

   Correct import = import { BrowserRouter, Routes, Route } from 'react-router-dom'; [OK]

Hint: Remember 'react-router-dom' exports BrowserRouter, Routes, Route [OK]

Common Mistakes:

• Using 'react-router' instead of 'react-router-dom'
• Mixing component names like Router instead of BrowserRouter
• Forgetting to import Routes component

3. Given this React routing code snippet, what will be displayed when the URL path is /about?

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    
      
        Home} />
        About Us} />
        Contact} />
      
    
  );
}

medium

A. Home

B. About Us

C. Contact

D. Nothing will be displayed

Solution

1. Step 1: Match URL path to Route path

   The URL path '/about' matches the Route with path='/about'.

2. Step 2: Identify the element rendered

   The Route for '/about' renders <h1>About Us</h1>.

3. Final Answer:

   <h1>About Us</h1> -> Option B

4. Quick Check:

   Path '/about' renders About Us [OK]

Hint: Match URL path exactly to Route path [OK]

Common Mistakes:

• Choosing the home route for all paths
• Confusing element props with children
• Assuming multiple routes render simultaneously

4. Identify the error in this React routing setup:

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Route path='/' element={} />
      <Routes>
        <Route path='/about' element={} />
      </Routes>
    </BrowserRouter>
  );
}

medium

A. Route components must be inside Routes component

B. BrowserRouter cannot wrap Routes

C. Route elements cannot use JSX components

D. Missing import for Home and About components

Solution

1. Step 1: Check Route placement

   All Route components must be children of a Routes component to work correctly.

2. Step 2: Identify the misplaced Route

   The Route with path='/' is outside the Routes component, which is incorrect.

3. Final Answer:

   Route components must be inside Routes component -> Option A

4. Quick Check:

   Routes wrap Route components [OK]

Hint: Always nest Route inside Routes [OK]

Common Mistakes:

• Placing Route outside Routes component
• Thinking BrowserRouter cannot wrap Routes
• Confusing JSX elements with strings in element prop

5. You want to create a navigation menu that updates the URL and shows the correct page without reloading. Which React Router component should you use for the links?

hard

A. <a> tags with href attribute

B. <button> with onClick calling window.location

C. <NavLink> component but without BrowserRouter

D. <Link> component from react-router-dom

Solution

1. Step 1: Understand navigation in React Router

   The <Link> component updates the URL and renders the new route without reloading the page.

2. Step 2: Evaluate options for SPA navigation

   <a> tags with href attribute causes full page reloads. <button> with onClick calling window.location uses window.location which reloads. <NavLink> component but without BrowserRouter requires BrowserRouter to work properly.

3. Final Answer:

   <Link> component from react-router-dom -> Option D

4. Quick Check:

   Use Link for client-side navigation [OK]

Hint: Use Link, not anchor tags, for SPA navigation [OK]

Common Mistakes:

• Using <a> tags causing full page reload
• Forgetting BrowserRouter wrapper for NavLink
• Using buttons with window.location causing reload