\n\u003Cimg width=\"1455\" height=\"345\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a66db53c-b90f-425a-9608-90b64e1ee248\" />",[3189,3192,3195],{"name":3190,"color":3191},"bug","d73a4a",{"name":3193,"color":3194},"v3","49DCB8",{"name":3196,"color":3197},"triage","ffffff",4666,"nuxt","ui","open","Nuxt UI v2 triggers full page reload on file changes when used as Nuxt module (Windows 11)","2025-08-05T11:02:17Z","https://github.com/nuxt/ui/issues/4666",0.68175864,{"description":3207,"labels":3208,"number":3212,"owner":3199,"repository":3199,"state":3201,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.9.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.23.0`\n- Nitro Version: `2.11.6`\n- Package Manager: `pnpm@9.5.0`\n- Builder: `-`\n- User Config: `ssr`, `devtools`, `compatibilityDate`, `css`, `app`, `modules`, `runtimeConfig`, `vite`, `vueQuery`, `ui`, `icon`, `elementPlus`\n- Runtime Modules: `@nuxt/eslint@1.2.0`, `@nuxt/icon@1.11.0`, `@nuxt/scripts@0.11.2`, `@nuxt/test-utils@3.17.2`, `@nuxt/ui@3.0.2`, `@element-plus/nuxt@1.1.1`, `@hebilicious/vue-query-nuxt@0.3.0`, `@vueuse/nuxt@13.0.0`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/purple-worker-q927r2?workspaceId=ws_Nd6bGHokakFXXgZBfRPLsD\n\n### Describe the bug\n\n**Steps to Reproduce:**\n\n1. Open the reproduction link.\n2. Click on 'page 2' at the top to navigate to the page2 page.\n3. The loading animation will not disappear.\n\nThe code logic of the page2 page is to call the `fetchData` function when the page is opened, while setting `loading` to true and then setting it to false within a short period.\n\nThis bug is triggered when a Nuxt page uses a transition with the mode set to `out-in`. Specifically, when the component's props change rapidly, the code related to DOM operations does not correctly handle the state of the props, resulting in abnormal component display.\n\nWorkaround:\n\n1. Set the mode to a value other than `out-in`.\n2. Wrap the component using `v-loading` with a `\u003CClientOnly>` component.\n3. Call `fetchData` within the `onMounted` callback.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```\n\nEdit: pick right words",[3209],{"name":3210,"color":3211},"pending triage","E99695",31613,"page transtion with fast props change","2025-04-02T03:30:33Z","https://github.com/nuxt/nuxt/issues/31613",0.6878697,{"description":3218,"labels":3219,"number":3221,"owner":3199,"repository":3199,"state":3201,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### 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_",[3220],{"name":3210,"color":3211},24763,"Inconsistencies when using multiple hybrid renderings","2024-06-30T11:06:36Z","https://github.com/nuxt/nuxt/issues/24763",0.6919111,{"labels":3227,"number":3234,"owner":3199,"repository":3199,"state":3235,"title":3236,"updated_at":3237,"url":3238,"score":3239},[3228,3230,3231],{"name":3229,"color":3197},"stale",{"name":3210,"color":3211},{"name":3232,"color":3233},"2.x","d4c5f9",5921,"closed","Problems with hard refresh in mode: universal with `nuxt generate`","2023-01-22T15:33:07Z","https://github.com/nuxt/nuxt/issues/5921",0.66379726,{"labels":3241,"number":3244,"owner":3199,"repository":3199,"state":3235,"title":3245,"updated_at":3246,"url":3247,"score":3248},[3242,3243],{"name":3210,"color":3211},{"name":3232,"color":3233},7247,"Direct access to a page generated with `yarn generate` shows the home page","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7247",0.672818,{"labels":3250,"number":3261,"owner":3199,"repository":3199,"state":3235,"title":3262,"updated_at":3263,"url":3264,"score":3265},[3251,3254,3255,3258],{"name":3252,"color":3253},"3.x","29bc7f",{"name":3190,"color":3191},{"name":3256,"color":3257},"pages","00DFB5",{"name":3259,"color":3260},"❗ p4-important","D93F0B",14475,"edge version is triggering re-renders on nested pages","2023-01-19T17:36:03Z","https://github.com/nuxt/nuxt/issues/14475",0.67790276,{"labels":3267,"number":3270,"owner":3199,"repository":3199,"state":3235,"title":3271,"updated_at":3272,"url":3273,"score":3274},[3268,3269],{"name":3210,"color":3211},{"name":3232,"color":3233},7829,"Issue in adding `pages/app.vue` file.","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7829",0.6801265,{"labels":3276,"number":3279,"owner":3199,"repository":3199,"state":3235,"title":3280,"updated_at":3281,"url":3282,"score":3283},[3277,3278],{"name":3210,"color":3211},{"name":3232,"color":3233},6500,"`nuxt build` fails at generating pages in spa mode","2023-01-22T15:34:46Z","https://github.com/nuxt/nuxt/issues/6500",0.6829146,{"description":3285,"labels":3286,"number":3288,"owner":3199,"repository":3199,"state":3235,"title":3289,"updated_at":3290,"url":3291,"score":3292},"I am having trouble with CSS and scripts breaking when refreshing my page, we are utilizing [Buefy UI](https://buefy.github.io/#/) . We are utilizing static generated structure running \"npm run generate\" in order to obtain static generate structure to deploy project as a static project. The project runs successfully and works when it comes to normal routes, when it starts. However, for some reason when I refresh the page the CSS breaks so does the functionality such as search or forms. This seems to be a routing issue as our URL changes when we refreshed and it adds a \"/\". It seems that based on the Nuxt static generate project structure. I am unable to change the routes as Nuxt builds my routes based on my pages folder structure. Does anyone have a solution or has gone through this? \r\n\r\nThe only configuration in our code for nuxt.configuration for the routes is the following below. This route is set up to display our initial page, which is the login page.\r\n ```\r\nrouter: {\r\n extendRoutes(routes, resolve) {\r\n routes.push({\r\n name: 'index',\r\n path: '/',\r\n component: resolve(__dirname, 'pages/login.vue')\r\n })\r\n torch.white(routes)\r\n }\r\n }, ```\r\n\r\n\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/c805\">#c805\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3287],{"name":3232,"color":3233},940,"Web application is breaking in functionality due to routing issues in Nuxt Static Generate.","2023-01-18T15:40:36Z","https://github.com/nuxt/nuxt/issues/940",0.682989,{"description":3294,"labels":3295,"number":3298,"owner":3199,"repository":3199,"state":3235,"title":3299,"updated_at":3300,"url":3301,"score":3302},"### 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",[3296,3297],{"name":3252,"color":3253},{"name":3210,"color":3211},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.687886,["Reactive",3304],{},["Set"],["ShallowReactive",3307],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQHicGtlv5QpK-LM-FSU5LxslL0Ikb50O4cXCTGgpMrQ":-1},"/nuxt/nuxt/3504"]