Deep links

Routes are paths, so wherever your app receives a link (a URL handler, a notification payload), hand the path to the router:

router.push('/messages/42')

That's safe on a cold start: a navigation requested before the first page is up waits for it and stacks on top, so back still lands on your home page.

Bringing the parents along

A link into a nested page can bring its parents along, so back walks up the app's hierarchy instead of jumping home:

router.push('/settings/account', { withParents: true })
// stack: / → /settings → /settings/account

The parents come from children nesting in the route table, and only those with a component become pages:

{
  path: '/settings',
  component: Settings,
  children: [{ path: 'account', name: 'account', component: Account }],
}

Parents already on top are skipped, only the last page animates, and guards run for every page. With clearHistory, the parents and the page become the whole stack. <RouterLink> takes withParents too.