\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[unhandledRejection] TypeError: dayjs.duration is not a function\n```",[2865,2868],{"name":2866,"color":2867},"pending triage","E99695",{"name":2869,"color":2870},"needs reproduction","FBCA04",31759,"nuxt","open","Nuxt 3.16.2 does not install settings from the module","2025-04-11T07:53:27Z","https://github.com/nuxt/nuxt/issues/31759",0.71162564,{"description":2879,"labels":2880,"number":2882,"owner":2872,"repository":2872,"state":2873,"title":2883,"updated_at":2884,"url":2885,"score":2886},"### 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",[2881],{"name":2866,"color":2867},31613,"page transtion with fast props change","2025-04-02T03:30:33Z","https://github.com/nuxt/nuxt/issues/31613",0.72025794,{"description":2888,"labels":2889,"number":2899,"owner":2872,"repository":2900,"state":2901,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Environment\n\nNuxtUI : 3.1.1\nNuxt: 3.17.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/calendar#color\n\n### Description\n\n\u003Cimg width=\"933\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8cbd8604-5bc2-4155-8136-f799f00fa693\" />",[2890,2893,2896],{"name":2891,"color":2892},"bug","d73a4a",{"name":2894,"color":2895},"v3","49DCB8",{"name":2897,"color":2898},"triage","ffffff",4084,"ui","closed","Incorrect display of \"Today\" in the calendar","2025-05-06T15:36:48Z","https://github.com/nuxt/ui/issues/4084",0.68617886,{"labels":2907,"number":2912,"owner":2872,"repository":2872,"state":2901,"title":2913,"updated_at":2914,"url":2915,"score":2916},[2908,2911],{"name":2909,"color":2910},"3.x","29bc7f",{"name":2866,"color":2867},13984,"Issue with v-calendar and nuxt 3","2023-01-19T17:11:34Z","https://github.com/nuxt/nuxt/issues/13984",0.70505106,{"description":2918,"labels":2919,"number":2923,"owner":2872,"repository":2900,"state":2901,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2920,2921,2922],{"name":2891,"color":2892},{"name":2894,"color":2895},{"name":2897,"color":2898},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.70706433,{"description":2929,"labels":2930,"number":2933,"owner":2872,"repository":2872,"state":2901,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v22.0.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.5.1\r\n- Builder: -\r\n- User Config: devtools, runtimeConfig, modules\r\n- Runtime Modules: @samk-dev/nuxt-vcalendar@1.0.3\r\n- Build Modules: -\n\n### Reproduction\n\nNot required IMO.\n\n### Describe the bug\n\nWhen I pass a date to my backend, the date that I received is now a string, which means I have to set the string to a date and after can call getDay, etc.\r\n\r\nconst response = await $fetch('/api/checkout', {\r\n method: 'POST',\r\n headers: {\r\n 'Content-Type': 'application/json',\r\n },\r\n body: JSON.stringify({\r\n startDate: new Date(range.value.start),\r\n endDate: new Date(range.value.end),\r\n }),\r\n });\r\n \r\n const { startDate, endDate }: CheckoutBody =\r\n await readBody(event);\r\n console.log(startDate.getDay());\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[request error] [unhandled] [500] startDate.getDay is not a function\n```\n",[2931,2932],{"name":2909,"color":2910},{"name":2866,"color":2867},27448,"Passing date from frontend to server","2024-06-04T23:07:56Z","https://github.com/nuxt/nuxt/issues/27448",0.7072255,{"description":2939,"labels":2940,"number":2943,"owner":2872,"repository":2872,"state":2901,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Environment\r\n\r\nNuxt project info: (copied to clipboard) 12:17:03 AM\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.8.1\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.2\r\n- Package Manager: npm@9.5.1\r\n- Builder: -\r\n- User Config: devtools, modules, googleSignIn\r\n- Runtime Modules: nuxt-vue3-google-signin@0.0.10\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 12:17:03 AM\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://n\r\n\r\n### Reproduction\r\n\r\nSB: https://stackblitz.com/edit/github-7tvhqt-cjjnim?file=app.vue\r\n\r\nRepo: https://github.com/kasvith/nuxt-vue3-google-signin-reproduce-bug\r\n\r\n**Note**: Use the repo as it provides some information on this behavior\r\n\r\n### Describe the bug\r\n\r\nAs users reported recently we got an issue with our plugin while loading runtime config in dev mode of nuxt.\r\nMost users were facing this issue randomly(sometimes it works, sometimes it doesn't) and it was very hard for us to even find whats wrong with our plugin.\r\n\r\nhttps://github.com/wavezync/nuxt-vue3-google-signin/blob/89e5ffcb5aa6761331c6775a4199caf3b76fed02/src/runtime/plugin.ts#L3-7\r\n\r\nIn our plugin we simply inject a value from runtime config to our standalone plugin.\r\n\r\n```js\r\nimport { defineNuxtPlugin, useRuntimeConfig } from '#app'\r\n\r\nexport default defineNuxtPlugin(async (nuxtApp) => {\r\n const { googleSignIn } = useRuntimeConfig().public\r\n if (googleSignIn) {\r\n const plugin = await import('vue3-google-signin')\r\n nuxtApp.vueApp.use(plugin.default, { clientId: googleSignIn.clientId })\r\n }\r\n})\r\n```\r\n\r\nand as user reports, the injected value randomly disappears and it make plugin unusable in dev mode.\r\n\r\n**Weird behavior**\r\n\r\nBy adding a simple `console.log` in the `node_modules/nuxt-vue3-google-signin/dist/runtime/plugin.mjs` it makes the plugin work normally\r\n\r\n```js\r\nimport { defineNuxtPlugin, useRuntimeConfig } from '#app'\r\n\r\nexport default defineNuxtPlugin(async (nuxtApp) => {\r\n console.log('here is a log') // this line fixed the issue\r\n const { googleSignIn } = useRuntimeConfig().public\r\n if (googleSignIn) {\r\n const plugin = await import('vue3-google-signin')\r\n nuxtApp.vueApp.use(plugin.default, { clientId: googleSignIn.clientId })\r\n }\r\n})\r\n```\r\n\r\n\r\n\r\nI was discussing this with @danielroe in discord before posting this issue here.\r\n\r\n**Related Issues**:\r\nhttps://github.com/wavezync/nuxt-vue3-google-signin/issues/14\r\nhttps://github.com/wavezync/nuxt-vue3-google-signin/issues/11\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2941,2942],{"name":2866,"color":2867},{"name":2869,"color":2870},24155,"Weird behavior when loading runtime values inside a plugin ","2024-11-08T23:02:00Z","https://github.com/nuxt/nuxt/issues/24155",0.70754224,{"labels":2949,"number":2954,"owner":2872,"repository":2872,"state":2901,"title":2955,"updated_at":2956,"url":2957,"score":2958},[2950,2951],{"name":2866,"color":2867},{"name":2952,"color":2953},"2.x","d4c5f9",4944,"Nuxt 2.4 will keep the build hanging with intervals and/or open connections","2023-01-22T15:33:01Z","https://github.com/nuxt/nuxt/issues/4944",0.70978546,{"description":2960,"labels":2961,"number":2970,"owner":2872,"repository":2900,"state":2901,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\n\nNuxt project info: (copied to clipboard) nuxi 10:36:44\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, experimental, nitro, sourcemap, ssr, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.1, @nuxtjs/mdc@0.15.0, @vueuse/nuxt@13.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n\nInput Menu Send an event when using @Change\n\n\n\nBut it is scheduled to send a value and this generates the error in console\n\n\n\n\n\n### Description\n\nhttps://github.com/user-attachments/assets/3fdd5798-3f77-45e0-a86b-18a2195219f2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2962,2963,2965,2966,2967],{"name":2891,"color":2892},{"name":2869,"color":2964},"CB47CF",{"name":2894,"color":2895},{"name":2897,"color":2898},{"name":2968,"color":2969},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.709887,{"labels":2976,"number":2979,"owner":2872,"repository":2872,"state":2901,"title":2980,"updated_at":2981,"url":2982,"score":2983},[2977,2978],{"name":2866,"color":2867},{"name":2952,"color":2953},8143,"[Vue-router] Update query param through computed is delayed (not reproduced with vanilla Vue)","2023-01-22T15:38:17Z","https://github.com/nuxt/nuxt/issues/8143",0.71124476,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuKl7Px1slIivswD8cdzhzwoUY6KCl5WEK8mvHPZSxVg":-1},"/nuxt/ui/4290"]