React Router overview - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the main React Router component for routing.

React

import { [1] } from 'react-router-dom';

Drag options to blanks, or click blank then click option'

AuseEffect

BuseState

CBrowserRouter

DReactDOM

Attempts:

3 left

💡 Hint

Common Mistakes

Importing hooks like useState instead of router components.

Confusing ReactDOM with routing components.

The BrowserRouter component is the main router component that enables routing in React apps.

2fill in blank

medium

Complete the code to define a route that renders the Home component at the root path.

React

<Route path='[1]' element={<Home />} />

Drag options to blanks, or click blank then click option'

A/

B/home

C/index

D/main

Attempts:

3 left

💡 Hint

Common Mistakes

Using '/home' instead of '/' for the root path.

Confusing path names with component names.

The root path '/' matches the home page URL.

3fill in blank

hard

Fix the error in the code to correctly render the routes inside the router.

React

return (
  <BrowserRouter>
    <[1]>
      <Route path='/' element={<Home />} />
      <Route path='/about' element={<About />} />
    </[1]>
  </BrowserRouter>
);

Drag options to blanks, or click blank then click option'

ARoutes

BSwitch

CRouter

DRoute

Attempts:

3 left

💡 Hint

Common Mistakes

Using which is deprecated in React Router v6.

Using as a wrapper instead of .

The Routes component wraps all Route elements in React Router v6+.

4fill in blank

hard

Fill both blanks to create a link that navigates to the About page.

React

<[1] to='[2]'>About</[1]>

Drag options to blanks, or click blank then click option'

ALink

BNavLink

C/about

D/contact

Attempts:

3 left

💡 Hint

Common Mistakes

Using when is sufficient here.

Setting the wrong path in the 'to' attribute.

The Link component creates navigation links, and the to prop sets the target path.

5fill in blank

hard

Fill all three blanks to extract the 'id' parameter from the URL using React Router hooks.

React

import { [1] } from 'react-router-dom';

function Item() {
  const params = [2]();
  return <p>Item ID: {params.[3]</p>;
}

Drag options to blanks, or click blank then click option'

AuseParams

BuseLocation

Cid

Dpathname

Attempts:

3 left

💡 Hint

Common Mistakes

Using useLocation which returns the URL object, not params.

Accessing 'pathname' instead of the parameter name.

The useParams hook returns URL parameters as an object. Access the 'id' parameter to show it.

Practice

1. What is the main purpose of React Router in a React application?

easy

A. To style React components with CSS

B. To create multiple pages without reloading the browser

C. To manage state across components

D. To fetch data from APIs

Solution

1. Step 1: Understand React Router's role

   React Router helps build apps with multiple pages by changing views without full page reloads.

2. Step 2: Compare with other options

   Styling, state management, and data fetching are handled by other tools, not React Router.

3. Final Answer:

   To create multiple pages without reloading the browser -> Option B

4. Quick Check:

   React Router = multi-page navigation without reload [OK]

Hint: React Router = multi-page navigation without full reload [OK]

Common Mistakes:

• Confusing React Router with CSS or styling tools
• Thinking React Router manages data fetching
• Assuming React Router handles state management

2. Which of the following is the correct way to wrap your app with React Router for browser-based routing?

easy

A. <BrowserRouter>...</BrowserRouter>

B. <Link>...</Link>

C. <Route>...</Route>

D. <Router>...</Router>

Solution

1. Step 1: Identify the main router component

   For browser history routing, React Router uses BrowserRouter to wrap the app.

2. Step 2: Understand other components

   Route defines pages, Link creates navigation links, and Router alone is not a valid component.

3. Final Answer:

   <BrowserRouter>...</BrowserRouter> -> Option A

4. Quick Check:

   BrowserRouter wraps app for browser routing [OK]

Hint: Wrap app with <BrowserRouter> for browser routing [OK]

Common Mistakes:

• Using <Router> instead of <BrowserRouter>
• Confusing <Route> with the router wrapper
• Wrapping app with <Link> which is for navigation

3. Given this React Router setup, what will be rendered when the URL path is /about?

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

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

medium

A. The component

B. Nothing renders because of missing default route

C. Both and components

D. The component

Solution

1. Step 1: Match URL path with Route path

   The URL /about matches the route with path='/about', so <About /> renders.

2. Step 2: Understand route exclusivity

   Only the matching route's element renders; <Home /> renders only at /.

3. Final Answer:

   The <About /> component -> Option D

4. Quick Check:

   URL '/about' renders About component [OK]

Hint: URL path matches Route path exactly to render component [OK]

Common Mistakes:

• Thinking both components render simultaneously
• Assuming missing default route breaks rendering
• Confusing '/' path with '/about'

4. Identify the error in this React Router code snippet:

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

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

medium

A. <Route> must be inside <Routes>

B. Missing closing tag for <BrowserRouter>

C. The <Route> for '/' should not have an element prop

D. Cannot use <Route> and <Routes> together

Solution

1. Step 1: Check component nesting rules

   In React Router, all <Route> components must be children of <Routes>.

2. Step 2: Identify incorrect placement

   The <Route path='/' ... /> is outside <Routes>, which is invalid.

3. Final Answer:

   <Route> must be inside <Routes> -> Option A

4. Quick Check:

   Routes wrap Route components [OK]

Hint: Always put <Route> inside <Routes> component [OK]

Common Mistakes:

• Placing <Route> outside <Routes>
• Thinking <Route> can be used alone
• Confusing element prop usage

5. You want to create a navigation menu that changes the URL without reloading the page. Which React Router component should you use, and why? Choose the best option.

hard

A. Use <Route> because it defines the navigation links

B. Use <a> tags because they are standard HTML links

C. Use <Link> because it updates the URL and renders the new page without reload

D. Use <BrowserRouter> because it creates the navigation menu

Solution

1. Step 1: Identify component for navigation links

   <Link> is designed to change the URL and render new pages without reloading.

2. Step 2: Compare with other options

   <a> causes full page reload, <Route> defines pages, and <BrowserRouter> wraps the app but does not create links.

3. Final Answer:

   Use <Link> because it updates the URL and renders the new page without reload -> Option C

4. Quick Check:

   Use Link for smooth navigation without reload [OK]

Hint: Use <Link> for navigation to avoid full page reload [OK]

Common Mistakes:

• Using <a> tags causing full reload
• Confusing <Route> with navigation links
• Thinking <BrowserRouter> creates menus