\r\n \u003C/template>\r\n\r\nAfter that page transitions stopped working completely. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1559\">#c1559\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2890],{"name":2869,"color":2870},1737,"Route transitions do not work inside nuxt-child ","2023-01-18T15:54:44Z","https://github.com/nuxt/nuxt/issues/1737",0.65723884,{"labels":2897,"number":2900,"owner":2872,"repository":2872,"state":2873,"title":2901,"updated_at":2902,"url":2903,"score":2904},[2898,2899],{"name":2866,"color":2867},{"name":2869,"color":2870},8385,"Await fetch calls during transition (simulating asyncData)","2024-06-14T16:04:01Z","https://github.com/nuxt/nuxt/issues/8385",0.66226643,{"description":2906,"labels":2907,"number":2911,"owner":2872,"repository":2872,"state":2873,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, compatibilityDate, app, dir, alias, modules, css, hooks, viewport, image, primevue, content, vite\r\n- Runtime Modules: @nuxt/eslint@0.3.13, @nuxt/image@1.7.0, nuxt-viewport@2.1.5, nuxt-primevue@3.0.0, @nuxt/content@2.13.2, @pinia/nuxt@0.5.3, @pinia-plugin-persistedstate/nuxt@1.2.1\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/devbox/compassionate-sammet-n7qj63\r\n\r\n### Describe the bug\r\n\r\nIm using page transition and when navigate for example from **\"user/1\"** to **\"user/2\"** page, my in page useAsyncData load some data from API's and update it **before new page transition comes in**. So, first the user sees the updated data and then the animation transition. This behavior causes ugly data flashes. It is normal or how to deal with it?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2908],{"name":2909,"color":2910},"pending triage","E99695",28913,"Page Transitions not synchronized with useAsyncData","2024-09-11T08:03:25Z","https://github.com/nuxt/nuxt/issues/28913",0.6637289,{"description":2917,"labels":2918,"number":2923,"owner":2872,"repository":2872,"state":2873,"title":2924,"updated_at":2893,"url":2925,"score":2926},"## Problem\r\nOn our index page we have a `\u003Cnuxt-child />` outlet in order to render the main page and display a login modal if the user navigates to /login. The login page is basically just a modal that gets plopped into the `\u003Cnuxt-child />` outlet.\r\n\r\nThe index page component has an asyncData method that makes an expensive api call. When the login modal is closed the router goes back to the parent route. `/login => /`\r\nAt this point asyncData is triggered again even when it's already rendered underneath.\r\n\r\n## Expectation\r\nExpected behavior would for asyncData to not trigger as the parent route was never really exited and it should just maintain its existing state.\r\n\r\n## Solution\r\nI have a hacky workaround in our index#asyncData method as seen here\r\n``` javascript\r\nasyncData ({ from, route }) {\r\n const routeName = route.name\r\n\r\n if (from && from.name.indexOf(routeName) === 0) {\r\n return Promise.resolve({})\r\n }\r\n\r\n return apiService.makeCall().then(({ data }) => data)\r\n}\r\n```\r\n\r\nThis seems to solve the issue but I'm just curious if always calling asyncData is intended behavior or not. Or otherwise a better solution that I'm not seeing.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1578\">#c1578\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2919,2922],{"name":2920,"color":2921},"question","cc317c",{"name":2869,"color":2870},1756,"Going 'back' from a nested child route triggers async data in the parent","https://github.com/nuxt/nuxt/issues/1756",0.66569424,{"labels":2928,"number":2934,"owner":2872,"repository":2872,"state":2873,"title":2935,"updated_at":2936,"url":2937,"score":2938},[2929,2932,2933],{"name":2930,"color":2931},"stale","ffffff",{"name":2909,"color":2910},{"name":2869,"color":2870},7814,"Child routes transitions error","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7814",0.6664837,{"labels":2940,"number":2942,"owner":2872,"repository":2872,"state":2873,"title":2943,"updated_at":2944,"url":2945,"score":2946},[2941],{"name":2869,"color":2870},6082,"Advanced route transition next/previous swipe feature on mobile ","2023-01-18T20:35:41Z","https://github.com/nuxt/nuxt/issues/6082",0.66861874,{"description":2948,"labels":2949,"number":2951,"owner":2872,"repository":2872,"state":2873,"title":2952,"updated_at":2953,"url":2954,"score":2955},"If I prevent a route change with `routeBeforeUpdate` method (as on vue-router spec) it seems `asyncData` for the new route (that has not been shown) is still called.\r\n\r\nIt looks as though `routeBeforeLeave` works fine, but as I need to prevent a route change when a slug/prop of a URL changes I need to use `routeBeforeUpdate`.\r\n\r\nIs there a simple check that can be put in place to make sure the new route is definitely going to be shown before `asyncData` is called?\r\n\r\nAlso, if the new route is not shown, and then it is allowed to be shown, asyncData isn't called I think because NuxtJS believes that route is already being shown (or it looks that way just seeing outputs when logging to the console)",[2950],{"name":2869,"color":2870},1146,"Route change prevented with beforeRouteUpdate still calls asyncData","2023-01-18T15:40:52Z","https://github.com/nuxt/nuxt/issues/1146",0.6722004,{"description":2957,"labels":2958,"number":2960,"owner":2872,"repository":2872,"state":2873,"title":2961,"updated_at":2962,"url":2963,"score":2964},"Is it possible to use the default transition mode, simultaneous, with nuxt routes? I can only get in-out and out-in working. I'd like both animations to run in parallel, with both routes in the dom at the same time.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1470\">#c1470\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2959],{"name":2869,"color":2870},1647,"Simultaneous route transition","2023-01-18T15:42:07Z","https://github.com/nuxt/nuxt/issues/1647",0.67367727,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdewiwOAkR-YJ95Sr68dxj81wyD-7YZHqDOc7zw4bBQM":-1},"/nuxt/nuxt/2012"]