#title Weekly Vue News #81 - Re-Rendering Vue Routes When Path Parameters Change #preview Ready for your weekly Vue & Nuxt dose?
Re-Rendering Vue Routes When Path Parameters Change
Hi 👋
I had to switch from
The paid plan for Cloudinary would be 99€/month 🤯 Therefore, I moved all images to an AWS S3 bucket and let them process them via
I'm busy producing Vue & Nuxt tips for upcoming newsletter issues.
Unfortunately, I also have a full backlog of blog post articles I would like to write...
Too many ideas, too little time 😥
Have a lovely week ☀️
To support me:
- 😘 Recommend the newsletter to your friends: it really helps!
- 💸 Sponsor the newsletter
- 🧵 Retweet the latest Twitter thread
- 📨 Reply to this email: feedback is welcome
In Vue applications, we use
A typical use case is a dynamic route pattern with params: /users/:id. It allows you to specify a parameter in the URL. The :id in this route pattern is a placeholder for a dynamic value, which can change based on the user's actions. Typically you will trigger a backend endpoint with the given id to fetch user details.
Let's take a look at an example:
The demo code of this article is interactively available in the following StackBlitz project:
<script setup>
import { ref, onMounted } from 'vue'
import { useRoute, useRouter } from 'vue-router'
import UserId from '@/components/UserId.vue'
import { getUserDetails } from '../api/userApi.js'
const route = useRoute()
const router = useRouter()
const loading = ref(false)
const details = ref(null)
async function fetchDetails(id) {
loading.value = true
try {
details.value = await getUserDetails(id)
} catch (error) {
console.error('Failed to fetch details', error)
details.value = 'Error'
} finally {
loading.value = false
}
}
function navigateToNextUser() {
const nextId = Number(route.params.id) + 1
router.push({ name: 'UserDetails', params: { id: nextId } })
}
onMounted(async () => {
console.log('UserDetails mounted')
fetchDetails(route.params.id)
})
</script>
<template>
<h2>User Details</h2>
<div>
<span>ID: {{ route.params.id }}</span>
<span v-if="loading">Loading details ...</span>
<span v-else>Details: {{ details }}</span>
<button @click="navigateToNextUser">Next User</button>
</div>
</template>
This component uses the onMounted lifecycle hook to fetch user details when the component is mounted. The user's ID is read via route.params.id from the useRoute composable.
So far, everything works fine and the user details are visible and they get updated if we update the route path manually by changing /users/1 to /users/2.
But our component contains a button that triggers a programmatic route update using router.push.
Programmatically altering the path does not trigger the re-rendering of the view. As a result, the mounted() hooks do not fire, and the nested components do not reload, leading to unexpected behavior.
Solution 1: Watcher
The simplest solution is to add a
<script setup>
// ...
watch(
() => route.params.id,
(newId, oldId) => {
fetchDetails(route.params.id)
}
)
</script>
Solution 2: Route Guard
Another solution is the
<script setup>
// ...
onBeforeRouteUpdate(async (to, from) => {
if (to.params.id !== from.params.id) {
fetchDetails(route.params.id)
}
})
</script>
Of course, you can also use the
It adds a navigation guard that triggers whenever the current location is about to be updated. Similar to beforeRouteUpdate but can be used in any component. The guard is removed when the component is unmounted.
Difference Between Solution 1 & 2
There is a big difference between using watch and beforeRouteUpdate:
The route guard is called before the value of the route object actually changes. The watcher is called after the value of route has changed.
Using the beforeRouteUpdate navigation guard, you can determine whether or not you want to prevent the route from changing or go to a different route entirely.
| 👉🏻 Volar, previously the official Vue VSCode extension, is now an embedded language tooling framework. |
| 👉🏻 It can process any file format that involves embedded languages. |
| 👉🏻 In this article, you'll learn how to create a reporting app with Vue 3 and Composition API. |
| 👉🏻 Flexmonster Pivot Table & Charts and Highcharts libraries are used. |
👉🏻 In this article, Fotis investigates different options to create transitions and micro-interactions.
fadamakis.com| 👉🏻 Evan You tells us what to expect in 2023 from Vue.js. |
| 👉🏻 He is the creator of the JavaScript framework Vue.js and the frontend build tool Vite. |
| 👉🏻 Responsive scrollable videos without obscure video encoding requirements. |
| 👉🏻 Compatible with React, Svelte, Vue, or just plain HTML. |
👉🏻 Adds enhanced support when inspecting Vue source
developer.chrome.com| 👉🏻 Chrome tracing lets you record a performance trace that captures low-level details of what the browser is doing. |
| 👉🏻 This post is a short guide on how to use this tool, from a web developer’s point of view. |
👉🏻 Veracode’s State of Software Security report for 2023 found that JavaScript Applications Have Fewer Security Flaws Than Java and .NET Applications.
www.infoq.com| 👉🏻 A compiled-away, type-safe, readable RegExp alternative. |
| 👉🏻 |
👉🏻 Nix is a tool that builds packages in isolation from each other to ensure that they are reproducible and don't have undeclared dependencies.
zero-to-nix.comUntil next week,
Holzapfelkreuther Str. 19, 81375 Munich, Germany
