if leaving nested route, child page is unmounted before suspense resolves

[danielroe]

stackblitz.com/edit/github-f4gpfk-qhgrfy?file=pages/test.vue

#13814 (comment)

[daehyun-thevc]

I am having a similar problem. Only the child page, not parent, of the new nested route are being set up before page:start so child can't receive props properly from async parent. After page:start, both parent and child implement each setup, so it looks fine but error printed in console.

[danielroe]

@daehyun-thevc would you post a reproduction so when we resolve this we can verify your use case is also covered?

[daehyun-thevc]

https://stackblitz.com/edit/github-szoey5?file=pages/index.vue
when navigating from /basecamp to /mountain which is async nested route, mountain/index.vue implements setup function before mountain.vue implements setup function, so there is undefined prop mountain

[Luffyyy]

I know this is being a bit pushy, but this issue is kinda related to the suspensible issue that Vue 3.3 fixed, but unfortunately hasn't fixed that specifically. I'd totally appreciate it (and I hope more that have this issue upvote it) if it got fixed already, I've been waiting months and this is the only major issue I have with Nuxt right now. 🚀

[emaung]

Heya yep. I agree that this needs a bit of priority. I am half way in my project and we keep building it hoping this will be fixed soon. Just that user experience is not very good with half of the page missing whenever change route.

Is there any workaround during the meantime?

Btw, totally appreciate and thank you for the time and effort you guys are putting in to bring this brilliant library.