\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>",[3048],{"name":3027,"color":3028},1737,"Route transitions do not work inside nuxt-child ","2023-01-18T15:54:44Z","https://github.com/nuxt/nuxt/issues/1737",0.65723884,{"labels":3055,"number":3058,"owner":3030,"repository":3030,"state":3031,"title":3059,"updated_at":3060,"url":3061,"score":3062},[3056,3057],{"name":3024,"color":3025},{"name":3027,"color":3028},8385,"Await fetch calls during transition (simulating asyncData)","2024-06-14T16:04:01Z","https://github.com/nuxt/nuxt/issues/8385",0.66226643,{"description":3064,"labels":3065,"number":3069,"owner":3030,"repository":3030,"state":3031,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### 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_",[3066],{"name":3067,"color":3068},"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":3075,"labels":3076,"number":3081,"owner":3030,"repository":3030,"state":3031,"title":3082,"updated_at":3051,"url":3083,"score":3084},"## 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>",[3077,3080],{"name":3078,"color":3079},"question","cc317c",{"name":3027,"color":3028},1756,"Going 'back' from a nested child route triggers async data in the parent","https://github.com/nuxt/nuxt/issues/1756",0.66569424,{"labels":3086,"number":3092,"owner":3030,"repository":3030,"state":3031,"title":3093,"updated_at":3094,"url":3095,"score":3096},[3087,3090,3091],{"name":3088,"color":3089},"stale","ffffff",{"name":3067,"color":3068},{"name":3027,"color":3028},7814,"Child routes transitions error","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7814",0.6664837,{"labels":3098,"number":3100,"owner":3030,"repository":3030,"state":3031,"title":3101,"updated_at":3102,"url":3103,"score":3104},[3099],{"name":3027,"color":3028},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":3106,"labels":3107,"number":3109,"owner":3030,"repository":3030,"state":3031,"title":3110,"updated_at":3111,"url":3112,"score":3113},"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)",[3108],{"name":3027,"color":3028},1146,"Route change prevented with beforeRouteUpdate still calls asyncData","2023-01-18T15:40:52Z","https://github.com/nuxt/nuxt/issues/1146",0.6722004,{"description":3115,"labels":3116,"number":3118,"owner":3030,"repository":3030,"state":3031,"title":3119,"updated_at":3120,"url":3121,"score":3122},"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>",[3117],{"name":3027,"color":3028},1647,"Simultaneous route transition","2023-01-18T15:42:07Z","https://github.com/nuxt/nuxt/issues/1647",0.67367727,["Reactive",3124],{},["Set"],["ShallowReactive",3127],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdewiwOAkR-YJ95Sr68dxj81wyD-7YZHqDOc7zw4bBQM":-1},"/nuxt/nuxt/2012"]