React Essentials · Routing Basics · Lesson 21 of 26
Why Client-Side Routing?
Concept
Why Client-Side Routing?
A single-page app has one HTML file, so a router swaps which component renders based on the URL, without a full page reload.
By the end of this lesson
- Explain the core idea behind Why Client-Side Routing?.
- Predict output before running a change.
- Test one realistic and one unusual input.
- Use the result to make the next decision.
How to study this page
- 1. Read one concept.
- 2. Change the example.
- 3. Run, compare, and explain.
- 4. Complete the challenge below.
ExampleRunnable
// Without a router: one static page
// With a router: URL decides which component shows
// "/" -> <Home />
// "/courses" -> <Courses />Try it Yourself »Self-check before continuing
Without looking at the example, describe what changes when you modify one input in Why Client-Side Routing?. Then reopen the editor and prove your explanation with a small test.
You are ready to continue when you can predict, test, and explain the result.
Your turn
List three URLs your own app would need and which component each should render.
Loading editor…
Console