[Bug report] Route path is not correct when navigating

[Mister-Hope]

Description

When accessing route.path at onMounted lifecycle, the value is the previous page, and this is not an expected behavior:

• watcher for route will be triggered unexpected
• a component will initialized with a route path it doesnot belong to

A normal vue app is working as expected: https://stackblitz.com/edit/vitejs-vite-ssyfup?file=src%2Fcomponents%2FB.vue,src%2Fcomponents%2FC.vue,src%2Fcomponents%2FHome.vue&terminal=dev

Reproduction

https://stackblitz.com/edit/vuepress-ewt9uy?file=docs%2Fguide%2FREADME.md

Used Package Manager

npm

System Info

Not needed

[Mister-Hope]

@meteorlxy I found further issue with this. Besides route.path has a delay with page change,

When navigating from different layout, the route path initial value will be undefined, then to old value , then to new value

E.g.:

when navigating from / (layout: Home) to /test (layout: Page)

Layout Page is watching route.path, then it will be trigger twice:

• undefined to /
• / to /test

Can we fix ASAP?

[Mister-Hope]

@meteorlxy Any suggestions on this one? I have made plenty of related workaround.

This mainly breaks any feature related with route path and query