` 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",[3031],{"name":3019,"color":3020},32371,"Using pageTransition/layoutTransition and useAsyncData() leads to faulty double-mounting","2025-06-12T11:44:20Z","https://github.com/nuxt/nuxt/issues/32371",0.6859353,{"description":3038,"labels":3039,"number":3041,"owner":3022,"repository":3022,"state":3023,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Environment\n\n````\n------------------------------\n- Operating System: Ubuntu 24.04 LTS\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.6.12\n- Builder: -\n- User Config: extends, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n````\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/martinszeltins/nuxt-component-already-mounted\n\n### Describe the bug\n\nI have a simple Nuxt app. I have a page with a `\u003CNuxtLink>` to another page. On the other page there is a composable which makes 2 API requests when you enter the page. But I am getting this warning in the console:\n\n````\nuseSingleShipmentFormInitialData.ts:6 [nuxt] [useFetch] Component is already mounted, please use $fetch instead. See https://nuxt.com/docs/getting-started/data-fetching\nuseSingleShipmentFormInitialData\t@\tuseSingleShipmentFormInitialData.ts:6\nawait in useSingleShipmentFormInitialData\t\t\n(anonymous)\t@\tsingle-shipment.vue:10\nsetup\t@\tsingle-shipment.vue:10\nShow 39 more frames\n````\n\nThe component couldn't possibly be already mounted because both API calls are awaited one after another.\n\nI don't have anything fancy going on. I am using layers and I have set `asyncContext: true` in nuxt.config.ts. That's about it. Please see the reproduction.\n\n_Note: It may not work in Stackblitz, so you might need to download the repo and try it locally._\n\n**Screenshot:**\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3040],{"name":3019,"color":3020},31058,"Bug: [nuxt] [useFetch] Component is already mounted, please use $fetch instead","2025-03-17T14:20:33Z","https://github.com/nuxt/nuxt/issues/31058",0.6980174,{"description":3047,"labels":3048,"number":3053,"owner":3022,"repository":3022,"state":3023,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### 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```",[3049,3050],{"name":3019,"color":3020},{"name":3051,"color":3052},"possible regression","B90A42",31479,"Pages being hot-reloaded twice","2025-03-20T17:53:46Z","https://github.com/nuxt/nuxt/issues/31479",0.7009075,{"description":3059,"labels":3060,"number":3063,"owner":3022,"repository":3064,"state":3023,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Environment\n\nI got this on my project, but was able to reproduce it on the stackblitz starter. Here's the info from there:\n\n```\nWorking directory: /home/projects/github-rg6uhsqu nuxi 15:08:38\nNuxt project info: nuxi 15:08:38\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 4.0.1\n- CLI Version: 3.26.4\n- Nitro Version: 2.12.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: devtools, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nReproduction: https://stackblitz.com/edit/github-rg6uhsqu?file=components%2Ftests%2FMyComponent.spec.ts\n\n1. Run `npm run test`\n2. See that the `console.log` from the watcher triggers both from Component 1 and Component 2; even though the state is only changed in the second test\n3. Unmounting the first wrapper within it's `it` block fixes the issue\n\n### Describe the bug\n\nIt seems that wrappers do not unmount automatically after their it statements. I'm not sure if this is expected behaviour, but I wouldn't expect it and I'm worried that it can cause some data-contamination between tests and cause memory leaks?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3061],{"name":3019,"color":3062},"5D08F5",1367,"test-utils","Mounted components do not automatically unmount once the `it` statement finishes","2025-07-24T13:21:49Z","https://github.com/nuxt/test-utils/issues/1367",0.70397305,{"description":3070,"labels":3071,"number":3073,"owner":3022,"repository":3064,"state":3074,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.4.1\n- Builder: -\n- User Config: compatibilityDate, devtools, future, srcDir, serverDir, dir, appId, app, modules, ssr, css, esbuild, vite, typescript, vue, postcss, phosphor, alias, components, imports, sentry, sourcemap, nitro, hooks\n- Runtime Modules: @nuxt/test-utils/module@3.19.1, @pinia/nuxt@0.11.1, @sentry/nuxt/module@9.29.0, @vee-validate/nuxt@4.15.1, @vueuse/nuxt@13.3.0, nuxt-phosphor-icons@1.3.0\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/p2qm2h\n\n- run `npm run test`\n- see that the options API test fails as no events are captured when using `mountSuspended`\n- see that it works correctly when using `mount` from @vue/test-utils\n\n### Describe the bug\n\nInitial events are not captured when using options API inside a component.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3072],{"name":3019,"color":3062},1332,"closed","`mountSuspended` does not catch event emitted in immediate watcher with options API","2025-07-10T10:38:22Z","https://github.com/nuxt/test-utils/issues/1332",0.62761754,{"description":3080,"labels":3081,"number":3086,"owner":3022,"repository":3022,"state":3074,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Version\r\n\r\n[v2.6.2](https://github.com/nuxt.js/releases/tag/v2.6.2)\r\n\r\n### Reproduction link\r\n\r\n[https://codesandbox.io/s/wn7j570y85](https://codesandbox.io/s/wn7j570y85)\r\n\r\n### Steps to reproduce\r\n\r\nSimply click on button named \"Mounted triggered twice, see console\" and see in console.\r\n(reproducable only with css:false for transition)\r\n\r\n### What is expected ?\r\n\r\nmounted once\r\n\r\n### What is actually happening?\r\n\r\nmounted twice\r\n\r\n### Additional comments?\r\n\r\nThe bug is still present on last release 2.7.1\r\nIt can be fixed quickly ? it's really a brake on client-side performance.\r\n(Related : https://github.com/nuxt/nuxt.js/issues/5616)\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9188\">#c9188\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3082,3083],{"name":3019,"color":3020},{"name":3084,"color":3085},"2.x","d4c5f9",5703,"Mounted twice when layout change","2024-08-11T06:44:28Z","https://github.com/nuxt/nuxt/issues/5703",0.65838057,{"description":3092,"labels":3093,"number":3096,"owner":3022,"repository":3022,"state":3074,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Version\n\n[edge](https://github.com/nuxt.js/releases/tag/edge)\n\n### Reproduction link\n\n[https://gist.github.com/aldarund/8d555c3ddf11010579acda6aada81e5c](https://gist.github.com/aldarund/8d555c3ddf11010579acda6aada81e5c)\n\n### Steps to reproduce\n\nMounted called twice for component.\nIf remove `{items: []}` from fetch - it called only once.\nIf replace fetch with mounted - it called only once\n\n\n### What is expected ?\n\nmounted called once for component\n\n### What is actually happening?\n\nmounted called twice for component\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7753\">#c7753\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3094,3095],{"name":3019,"color":3020},{"name":3084,"color":3085},3899,"component mounted called twice when using global ","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3899",0.65967995,{"description":3102,"labels":3103,"number":3105,"owner":3022,"repository":3022,"state":3074,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\nWorking directory: /project/workspace 6:05:31 PM\nNuxt project info: 6:05:31 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.19\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/adoring-lederberg-873hwm\n\n1. Open the `/` page of the application.\n2. You will be redirected to the `/hello` page.\n3. Check the logs, and you will notice that the message `fire twice` is logged twice.\n\n\n### Describe the bug\n\nI have encountered a bug in my Nuxt application where the mounted hook on the /hello page is triggered twice under certain conditions.\n\n1. In `nuxt.config.ts`, I have set `app.pageTransition` and `app.layoutTransition`.\n2. On the `/` page, I am using a custom layout and triggering a redirect to the `/hello` page in the mounted hook.\n3. On the `/hello` page, I am calling the `Foo` component with lazy loading `\u003CLazyFoo />`.\n\nThese three factors seem to be causing the mounted hook in the `/hello` page to be triggered twice.\n\nThis issue does not occur if:\n\n1. Either `app.pageTransition`, `app.layoutTransition`, or both are set to false, or\n2. The `Foo` component is called without lazy loading `\u003CFoo />`.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3104],{"name":3019,"color":3020},30200,"`onMounted` hook triggered twice","2024-12-09T03:29:52Z","https://github.com/nuxt/nuxt/issues/30200",0.6608305,{"description":3111,"labels":3112,"number":3117,"owner":3022,"repository":3022,"state":3074,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-vqqsvj?file=pages%2Findex.vue\n\n### Describe the bug\n\nWhen we navigate with nuxt-link or router.push, onMounted on the page is invoked twice. You can see it in the console of reproduction. We just discovered this but it seems like it is also exist in 3.7.1 and 3.7.4\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3113,3116],{"name":3114,"color":3115},"3.x","29bc7f",{"name":3019,"color":3020},23453,"onMounted invoked twice","2023-09-28T14:21:55Z","https://github.com/nuxt/nuxt/issues/23453",0.66811913,["Reactive",3123],{},["Set"],["ShallowReactive",3126],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ffJtyTpoGfdmX92VZdCk5Nw2Ua7EF-i6OKu392Yp4lfA":-1},"/nuxt/test-utils/1176"]