Route parameters with useRoute in Vue - Step-by-Step Execution

Concept Flow - Route parameters with useRoute

User navigates to URL with parameter

↓

Vue Router reads URL

↓

useRoute() hook accesses current route

↓

Extract parameter from route.params

↓

Component uses parameter to display data

↓

Rendered output updates with parameter value

This flow shows how Vue Router reads the URL, useRoute() accesses the current route, extracts parameters, and the component updates its display accordingly.

Execution Sample

Vue

import { useRoute } from 'vue-router'
import { computed } from 'vue'

export default {
  setup() {
    const route = useRoute()
    const id = computed(() => route.params.id)
    return { id }
  }
}

This code uses useRoute to get the current route and extracts the 'id' parameter to use in the component.

Execution Table

Step	Action	Route URL	route.params	Extracted id	Component Output
1	User navigates to /user/42	/user/42	{ id: '42' }	42	id = 42 displayed
2	useRoute() reads current route	/user/42	{ id: '42' }	42	id = 42 displayed
3	Component extracts id from route.params	/user/42	{ id: '42' }	42	id = 42 displayed
4	Component renders with id	/user/42	{ id: '42' }	42	Shows user ID: 42
5	User navigates to /user/99	/user/99	{ id: '99' }	99	Shows user ID: 99
6	Component updates with new id	/user/99	{ id: '99' }	99	Shows user ID: 99
7	User navigates to /user without id	/user	{}	undefined	Shows user ID: undefined
8	Component tries to extract id but none found	/user	{}	undefined	Shows user ID: undefined
9	Execution ends as user stops navigation	/user	{}	undefined	Final display with id undefined

💡 Execution stops when user stops navigating or component unmounts.

Variable Tracker

Variable	Start	After Step 1	After Step 5	After Step 7	Final
route.params	{}	{ id: '42' }	{ id: '99' }	{}	{}
id	undefined	42	99	undefined	undefined

Key Moments - 2 Insights

Why is id sometimes undefined in the component?

If the URL does not include the parameter (like /user without /:id), route.params.id is undefined, as shown in execution_table rows 7 and 8.

Does useRoute() update automatically when the URL changes?

Yes, useRoute() always reflects the current route, so when the user navigates to a new URL with a different parameter, the id updates as shown in rows 5 and 6.

Visual Quiz - 3 Questions

Look at the execution table at step 3. What is the value of id extracted from route.params?

A 99

B 42

C undefined

D {}

💡 Hint

Check the 'Extracted id' column at step 3 in the execution_table.

At which step does the component first display id as '99'?

A Step 2

B Step 7

C Step 5

D Step 8

💡 Hint

Look for 'Shows user ID: 99' in the 'Component Output' column.

If the user navigates to /user/123, what will route.params.id be?

A '123'

B '42'

C '99'

D undefined

💡 Hint

route.params.id matches the URL parameter after /user/ as shown in variable_tracker.

Concept Snapshot

Use useRoute() to access the current route object.
Extract parameters from route.params, e.g., route.params.id.
Parameters come from dynamic segments in the URL.
When URL changes, useRoute() updates automatically.
Use extracted params to render dynamic content.

Full Transcript

This visual execution shows how Vue Router's useRoute hook accesses the current route and extracts parameters from the URL. When a user navigates to a URL like /user/42, the route.params object contains { id: '42' }. The component uses useRoute() to get this object and extracts the id parameter to display it. If the user navigates to a different URL with a different id, useRoute() updates automatically and the component re-renders with the new id. If the URL lacks the parameter, the id is undefined. This flow helps beginners see how route parameters flow from the URL into the component's reactive data.

Practice

1. What does the useRoute function in Vue Router allow you to do inside a component?

easy

A. Access the current route's parameters and information

B. Change the URL path programmatically

C. Register a new route dynamically

D. Navigate to a different route without reloading

Solution

1. Step 1: Understand the purpose of useRoute

   useRoute is a Vue Router composable that provides access to the current route object inside a component.

2. Step 2: Identify what can be accessed with useRoute

   It allows reading route parameters, query, name, and path but does not change routes or register them.

3. Final Answer:

   Access the current route's parameters and information -> Option A

4. Quick Check:

   useRoute reads route info = B [OK]

Hint: useRoute reads route info, doesn't change or register routes [OK]

Common Mistakes:

• Thinking useRoute changes routes
• Confusing useRoute with useRouter
• Assuming useRoute registers routes

2. Which of the following is the correct way to import and use useRoute in a Vue 3 component's setup() function?

easy

A. import { useRoute } from 'vue-router'; const route = useRoute(route);

B. import useRoute from 'vue-router'; const route = useRoute();

C. import { useRoute } from 'vue-router'; const route = useRoute();

D. import { useRoute } from 'vue'; const route = useRoute();

Solution

1. Step 1: Check the import source

   useRoute is exported from 'vue-router', so import must be from 'vue-router'.

2. Step 2: Verify usage syntax

   The correct usage is calling useRoute() without arguments to get the current route object.

3. Final Answer:

   import { useRoute } from 'vue-router'; const route = useRoute(); -> Option C

4. Quick Check:

   Correct import and call = D [OK]

Hint: Import from 'vue-router' and call useRoute() with no arguments [OK]

Common Mistakes:

• Importing from 'vue' instead of 'vue-router'
• Calling useRoute with arguments
• Using default import instead of named import

3. Given this Vue 3 component code snippet, what will be logged when the URL is /user/42 and the route is defined as /user/:id?

import { useRoute } from 'vue-router';
import { onMounted } from 'vue';

export default {
  setup() {
    const route = useRoute();
    onMounted(() => {
      console.log(route.params.id);
    });
  }
}

medium

A. null

B. undefined

C. user

D. 42

Solution

1. Step 1: Identify the route parameter

   The route is defined as /user/:id, so id is a parameter expected in route.params.

2. Step 2: Check the URL and logged value

   The URL is /user/42, so route.params.id will be "42". The console logs this value on mount.

3. Final Answer:

   42 -> Option D

4. Quick Check:

   route.params.id = "42" [OK]

Hint: Route param matches URL segment after colon :id [OK]

Common Mistakes:

• Expecting param name instead of value
• Confusing params with query
• Logging before route is ready

4. What is the main issue with this Vue 3 component code that tries to react to route parameter changes?

import { useRoute } from 'vue-router';
import { computed } from 'vue';

export default {
  setup() {
    const route = useRoute();
    const userId = computed(() => route.params.id);
    return { userId };
  }
}

The component does not update userId when the route changes.

medium

A. The route object is not reactive, so computed won't update

B. The computed function is missing a dependency array

C. The useRoute hook must be called inside onMounted

D. The userId should be a ref, not computed

Solution

1. Step 1: Understand reactivity of route

   The route object returned by useRoute() is reactive, but its params property is not deeply reactive by default.

2. Step 2: Why computed does not update

   Because route.params is not reactive, the computed property does not track changes, so userId stays the same.

3. Final Answer:

   The route object is not reactive, so computed won't update -> Option A

4. Quick Check:

   Route params not reactive = A [OK]

Hint: Route params are not deeply reactive; watch route.fullPath instead [OK]

Common Mistakes:

• Assuming route.params is reactive
• Calling useRoute inside lifecycle hooks
• Using ref instead of computed incorrectly

5. You want to create a Vue 3 component that displays the user ID from the route parameter and updates automatically when the route changes. Which approach correctly achieves this?

import { useRoute } from 'vue-router';
import { computed, watch, ref } from 'vue';

export default {
  setup() {
    const route = useRoute();
    // What should userId be?
    const userId = ???
    return { userId };
  }
}

hard

A. computed(() => route.params.id)

B. computed(() => route.params.id) with a watch on route.fullPath to trigger updates

C. computed(() => route.fullPath.split('/')[2])

D. ref(route.params.id) without any watcher

Solution

1. Step 1: Understand reactivity limitations

   Route params are not deeply reactive, so computed(() => route.params.id) alone won't update when params change.

2. Step 2: Use a watch on route.fullPath to trigger updates

   Watching route.fullPath (which is reactive) and recomputing userId ensures updates when the route changes.

3. Final Answer:

   computed(() => route.params.id) with a watch on route.fullPath to trigger updates -> Option B

4. Quick Check:

   Watch route.fullPath for param changes = C [OK]

Hint: Watch route.fullPath to react to param changes in computed [OK]

Common Mistakes:

• Using computed alone without watch
• Parsing fullPath manually without reactivity
• Using ref without updating on route change