` inside a `\u003CSuspense>`.\n\n```html\n\u003CSuspense>\n \u003CNuxtPage />\n\u003C/Suspense>\n```\n\nThe Suspense Quick Fix seems to work fine. We have it in production now for about half a year. But I can't say if it has any drawbacks or creates issues elsewhere. It's also difficult to make sure our devs know of this workaround and do not create new pages without it.\n\n### Additional context\n\nThe issue was once further explained as a comment to https://github.com/nuxt/nuxt/issues/27364. The bug is open for +1 Year now. \n\nI updated the reproduction to 3.17.5 and the bug persists.\nI suggest closing the other, less clearly described issue and keep tracking this one.\n\nIf it's not an easy fix, then I would suggest that after 1 year, at least a warning in the documentation should be placed that page/layout transitions should be used with caution.\n\nRelated:\nhttps://github.com/nuxt/scripts/issues/297\nhttps://github.com/nuxt/nuxt/issues/27442\nhttps://github.com/nuxt/nuxt/issues/27364\n",[3020],{"name":3021,"color":3022},"pending triage","E99695",32371,"nuxt","open","Using pageTransition/layoutTransition and useAsyncData() leads to faulty double-mounting","2025-06-12T11:44:20Z","https://github.com/nuxt/nuxt/issues/32371",0.6583327,{"description":3031,"labels":3032,"number":3034,"owner":3024,"repository":3024,"state":3025,"title":3035,"updated_at":3036,"url":3037,"score":3038},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.11.0\r\n- Builder: -\r\n- User Config: devtools, routeRules\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nYou can check the following repo: https://github.com/mitjans/nuxt-route-rules\r\nThen, you can:\r\n\r\n1. Build the application: `nuxt build`\r\n2. Serve the application: `node .output/server/index.mjs`\r\n3. Send requests with [httpie](https://httpie.io/cli):\r\n `http :3000/spa`\r\n4. Check if the page is being rendered in the client or the server by looking at the node server's console logs and the httpie response (if the page comes rendered or not)\n\n### Describe the bug\n\nI've set up a simple Nuxt app with the following Nuxt config (and pages):\r\n\r\n```typescript\r\nexport default defineNuxtConfig({\r\n ssr: false,\r\n routeRules: {\r\n \"/static\": { static: true },\r\n \"/prerendered\": { prerender: true },\r\n \"/ssr\": { ssr: true },\r\n \"/spa\": { ssr: false },\r\n },\r\n});\r\n```\r\n\r\nThings I've noticed:\r\n\r\n- **❓[QUESTION]:** What happens when global `ssr: false` but a route-rule sets a specific `ssr: true`. My guess is that the global `ssr` has more priority and so the poge `/ssr`, although specified to be rendered in the server, will be rendered as an SPA in the client. This behavior is reproducible in the provided Nuxt app. Would be nice to have some explicit mention of this in the documentation.\r\n- **⁉️[QUESTION + POSSIBLE BUG]:** `static: true` is not listed in [the documentation](https://nuxt.com/docs/guide/concepts/rendering#route-rules). What's its effect? My guess:\r\n - When global or route `ssr: true`, it is hydrated at build time and served statically from the server\r\n - When global or route `ssr: false`, an HTML SPA application is created at build time, served statically, and hydrated on the client\r\n > 👆 if this is the case, it is not what I've been able to reproduce in the provided Nuxt app. In the first case, I see a `console.log('static page')` in the server, which means it is being hydrated in the server (?).\r\n- **❗[POSSIBLE BUG]:** when `prerendered: true`, I would expect the page to be hydrated at build time and served statically (like the first case in the previous point), regardless of the global or route `ssr` setting. This behavior is not reproducible in the provided Nuxt app:\r\n - When `ssr: false`: the page is served as an SPA (hydrated in the client)\r\n - When `ssr: true`: the page is correctly hydrated at build time and served statically\r\n\r\nOverall, my feeling is that there's a lack of documentation on how the rendering modes interact with each other. I would love to help and contribute to adding the missing documentation, but would like to first fully comprehend what's the expected behavior in each of the previous cases.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3033],{"name":3021,"color":3022},24763,"Inconsistencies when using multiple hybrid renderings","2024-06-30T11:06:36Z","https://github.com/nuxt/nuxt/issues/24763",0.6658834,{"description":3040,"labels":3041,"number":3046,"owner":3024,"repository":3024,"state":3025,"title":3047,"updated_at":3048,"url":3049,"score":3050},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v23.6.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: compatibilityDate, devtools, ssr\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://github.com/Jeffrieh/hotreload-bug\n\nrun with `dev` go to the index page (http://localhost:3000), update the code, and hot reload will reload/trigger the page twice.\n\n### Describe the bug\n\nupdating a page causes hotreload to trigger twice, once with macro=true in the url and once without, on a brand new nuxt install (3.16.1), downgrading to nuxt 3.14 fixes the problem.\n\n\n\nthis causes all the javascript to be ran twice, which causes a lot of weird/unexpected bugs.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3042,3043],{"name":3021,"color":3022},{"name":3044,"color":3045},"possible regression","B90A42",31479,"Pages being hot-reloaded twice","2025-03-20T17:53:46Z","https://github.com/nuxt/nuxt/issues/31479",0.6666851,{"description":3052,"labels":3053,"number":3058,"owner":3024,"repository":3024,"state":3059,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Environment\n\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.14.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `npm@8.3.1`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-55pbvb?file=pages/sample.vue\r\n\r\nLogs in the console:\r\n```\r\nCreating default layout\r\nCreating /\r\nMounted /\r\nTime to navigate to /sample\r\nCreating /sample\r\nMounted /sample\r\nCreating sample layout\r\nCreating /sample\r\nMounted /sample\r\n```\n\n### Describe the bug\n\nA page is being created and mounted 2 times when navigating with `navigateTo` for the first time to a page with a different layout. I think this is somehow related to nuxt/nuxt.js#14614 because when this bug happens I also do not get `data` or `error` from `useAsyncData`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3054,3057],{"name":3055,"color":3056},"3.x","29bc7f",{"name":3021,"color":3022},14712,"closed","Pages are created 2 times when navigating between pages with different layouts","2023-01-19T17:39:14Z","https://github.com/nuxt/nuxt/issues/14712",0.63267744,{"description":3065,"labels":3066,"number":3071,"owner":3024,"repository":3024,"state":3059,"title":3072,"updated_at":3073,"url":3074,"score":3075},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.15.8\r\n- node: v14.19.0\r\n\r\n### Reproduction\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\nhttps://codesandbox.io/p/github/Kolobok12309/nuxt-page-layout-mount-twice/draft/stoic-beaver - playground\r\nhttps://github.com/Kolobok12309/nuxt-page-layout-mount-twice - repo\r\n\r\n### Steps to reproduce\r\n\r\n1. Config nuxt\r\n```js\r\n// nuxt.config.js\r\nexport default {\r\n features: {\r\n transitions: false,\r\n },\r\n\r\n build: {\r\n splitChunks: {\r\n layouts: true,\r\n },\r\n },\r\n}\r\n```\r\n\r\n2. Create 2 layouts and 2 pages\r\n3. Add `console.log('mounted', this.$nuxt.layoutName)` to `mounted` hook of each page\r\n4. Go from one page to another\r\n\r\n\r\n### What is Expected?\r\n\r\n```\r\n// from page-1 to page-2\r\nmounted layout-2\r\n// page-2 to page-1\r\nmounted layout-1\r\n```\r\n\r\n\r\n### What is actually happening?\r\n\r\n```\r\n// from page-1 to page-2\r\nmounted layout-1\r\nmounted layout-2\r\n// page-2 to page-1\r\nmounted layout-2\r\nmounted layout-1\r\n```\r\n\r\n### Additional info\r\n\r\nIf i set `features.transitions: true`, all to be fine, but we can't use it(some problems with meta)",[3067,3068],{"name":3021,"color":3022},{"name":3069,"color":3070},"2.x","d4c5f9",10873,"Page mounted twice","2024-06-14T12:08:58Z","https://github.com/nuxt/nuxt/issues/10873",0.63507247,{"description":3077,"labels":3078,"number":3080,"owner":3024,"repository":3024,"state":3059,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.5\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools, ssr\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-1uighmye\n\nCheck the Browser console.\n\n### Describe the bug\n\nWhenever one navigates to another page, the new page renders twice. Is this intentional?\n\nIt happens with both SSR: true and SSR: false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3079],{"name":3021,"color":3022},31279,"Pages being rendered twice when navigating","2025-03-08T15:39:10Z","https://github.com/nuxt/nuxt/issues/31279",0.63881373,{"description":3086,"labels":3087,"number":3090,"owner":3024,"repository":3024,"state":3059,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-lxsrmg?file=pages/index.vue\r\n\r\n1. Visit Index\r\n2. Visit A\r\n3. Visit Index\r\n4. Visit B\r\n5. Visit Index\r\n\r\nObserve console messages\r\n\r\n### Describe the bug\r\n\r\nIf we navigate between pages with different layouts it looks like the `setup` method runs twice, including useAsyncData.\r\n\r\nI was not able to reproduce it, but additionally in my private project `data` is always `null` after the second run, which completely crashes the page. ",[3088,3089],{"name":3055,"color":3056},{"name":3021,"color":3022},14760,"Page component initiates twice after layout change","2023-01-19T17:39:45Z","https://github.com/nuxt/nuxt/issues/14760",0.6436242,{"labels":3096,"number":3102,"owner":3024,"repository":3024,"state":3059,"title":3103,"updated_at":3104,"url":3105,"score":3106},[3097,3100,3101],{"name":3098,"color":3099},"stale","ffffff",{"name":3021,"color":3022},{"name":3069,"color":3070},7830,"SplitChunks not working correctly?","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7830",0.6479233,{"description":3108,"labels":3109,"number":3112,"owner":3024,"repository":3024,"state":3059,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Environment\n\nNuxt project info: 10:47:31 AM\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.5\r\n- Builder: -\r\n- User Config: devtools, css, modules, tailwindcss, app\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.11.3, @nuxtjs/color-mode@3.3.2\r\n- Build Modules: -\n\n### Reproduction\n\nTo reproduce the issue: \r\n1. run `nuxt build` on [this project](https://github.com/AbandonTech/abandontechsite/tree/demo/broken-about-page) (ensure you are on the dedicated branch that has this issue). \r\n2. Navigate to the `About` page\r\n3. Navigate to any other page,\r\n4. Navigate back to the `About` page, duplicate pages will be rendered on the app and will continue infinitely as long as you keep navigating.\r\n\r\n(Currently the hosted version at https://demo.abandontech.cloud/ has this bug and I will refrain from updating it temporarily incase anyone would like to demo it live)\r\n(working on creating a minimal reproduction)\r\n\r\nThis is reproducible on linux and windows, in docker, and after building from a github action.\n\n### Describe the bug\n\nI am unable to find the specific cause of this issue, but when navigating between a specific, problem `page` (the about page), then navigating away from this page, then navigating back to the problem page, other pages will be duplicated/embedded on the application. The application enters a broken state where navigating to other pages (using NuxtLink) results in each new page being rendered on the existing screen/application and infinitely expanding\r\n\r\nTo fix the issue, the contents of the about.vue page can be wrapped in a single `div`, making the component ClientOnly, or using a NuxtIsland.\r\n\n\n### Additional context\n\nThe issue is only reproducible on the built version of the app. The issue is not observable when using `yarn dev` to run the project.\r\n\r\nThe hosted demo site complains about a hydration issue, but I have fixed the hydration issue and have confirmed the page duplication bug still exists.\r\n\r\nAttached is an image of the expected result of navigating to the `About` page as well as the result of navigating away and back to the `About` page many times \r\n\r\n\r\n\r\n\r\n\n\n### Logs\n\n```shell-script\nNo logs or error output generated\n```\n",[3110,3111],{"name":3055,"color":3056},{"name":3021,"color":3022},26706,"Routing to Nuxt page with multiple top-level divs on built project results in duplicate pages being rendered on one route/page","2025-01-10T03:51:42Z","https://github.com/nuxt/nuxt/issues/26706",0.64869374,{"labels":3118,"number":3122,"owner":3024,"repository":3024,"state":3059,"title":3123,"updated_at":3124,"url":3125,"score":3126},[3119,3120,3121],{"name":3098,"color":3099},{"name":3021,"color":3022},{"name":3069,"color":3070},7014,"Splitted layout with error page","2023-01-22T15:34:48Z","https://github.com/nuxt/nuxt/issues/7014",0.65526974,["Reactive",3128],{},["Set"],["ShallowReactive",3131],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4j93emZuphLDRT2NFU7ZRMxNUOwTEjoNFwEfH-oNcdM":-1},"/nuxt/nuxt/8328"]