\n \u003C/template>\n \u003Ctemplate #increment>\n \u003CUButton\n :loading=\"loadingInc\"\n variant=\"link\"\n icon=\"i-lucide-plus\"\n @click=\"loadingInc = true\"\n :ui=\"{\n base: 'text-gray-500 hover:text-[var(--ui-color-primary-500)] disabled:text-gray-500 cursor-pointer',\n }\"\n />\n \u003C/template>\n \u003C/UInputNumber>\n````\n\nbest,\ngregor\n\n### Additional context\n\n_No response_",[3217,3218],{"name":3138,"color":3139},{"name":3141,"color":3142},3159,"option to disable on press behaviour for increment/decrement for inputNumber component","2025-05-14T15:41:35Z","https://github.com/nuxt/ui/issues/3159",0.72441655,{"description":3225,"labels":3226,"number":3229,"owner":3147,"repository":3147,"state":3184,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.7.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.17\r\n- Builder: -\r\n- User Config: runtimeConfig, purgeCSS, modules, pinia, imports, i18n, dayjs, dayjsI18n, turnstile, app, meta, build, css\r\n- Runtime Modules: nuxt-icons@3.2.1, @nuxtjs/turnstile@0.6.3, @gabortorma/nuxt-dayjs-i18n@2.0.2, @nuxtjs/i18n@8.0.0-beta.13, dayjs-nuxt@2.1.9, @nuxtjs/tailwindcss@6.10.1, @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.2.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new \r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/devbox/dazzling-lake-wsdcds?file=%2Fpages%2Findex.vue%3A3%2C8\r\n\r\n### Describe the bug\r\n\r\ni dont know am i thinking wrong but this is the case.\r\n\r\ni am changing data which i am also using as a prop and after i change i am calling the function inside of component but prop data is not changing directly.\r\n\r\n---------\r\n\r\nThere is a main page file and inside of it i have \r\ndata object\r\n\r\ndata: {\r\n id:0\r\n}\r\n\r\nwhen i click the button i am changing this data objects id to 2 and i am calling the method inside component\r\n\r\nbut if you check the console you can see the data is still 0. \r\n\r\nit should be 2 because i did this\r\n\r\nthis.data.id = 2;\r\nthis.$refs[\"testref\"].conslog();\r\n\r\n\r\nif i use nexttick it is working btw\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3227,3228],{"name":3193,"color":3194},{"name":3169,"color":3196},24872,"Nuxt3 props and refs weird behaviour","2023-12-22T16:00:35Z","https://github.com/nuxt/nuxt/issues/24872",0.7245902,{"description":3235,"labels":3236,"number":3245,"owner":3147,"repository":3147,"state":3184,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n**VsCode 1.79.2**\r\n- vscode.typescript-language-features: disabled\r\n- Vue.volar: 1.8.3, enabled\r\n- Vue.vscode-typescript-vue-plugin: 1.8.3, enabled\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/niklas-may/nuxt-module-issue-reproduction\r\n\r\n### Describe the bug\r\n\r\n**Preface**\r\n_Thank you for your amazing work on Nuxt! I am not sure where this issue is best raised, Nuxt, VsCode or Vue. But due to the special typescript tooling with auto imports, I thought it's best to start here, and would be happy to hear if anybody observed a similar behaviour or has a solution._ \r\n\r\n**Description**\r\nWhen I open `~/.nuxt/components.d.ts` in VsCode and hover over an imported component, VsCode IntelliSense popover displays the correct types for this component.\r\nBut when I use the component in any other components template block, for example `~/app.vue`, the typing is missing the prop types.\r\n\r\n### Component and Type Definitions\r\n\r\n`~/../src/runtime/MyButton.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv style=\"border: 1px solid pink\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nwithDefaults(\r\n defineProps\u003C{\r\n variant: \"fill\" | \"ghost\";\r\n }>(),\r\n { variant: \"fill\" }\r\n);\r\n\u003C/script>\r\n```\r\n\r\n`~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\ndeclare module 'vue' {\r\n export interface GlobalComponents {\r\n //...\r\n 'MyButton': typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n //...\r\n }\r\n}\r\n\r\nexport const MyButton: typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n\r\nexport const componentNames: string[]\r\n```\r\n\r\n\r\n### Correct Intellisense\r\n\r\nVsCode popopver hovering `'MyButton'` in `~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\n(property) GlobalComponents['MyButton']: __VLS_WithTemplateSlots\u003CDefineComponent\u003C{\r\n variant: {\r\n type: PropType\u003C\"fill\" | \"ghost\">;\r\n required: true;\r\n default: string;\r\n };\r\n}, {}, unknown, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, ... 5 more ..., {}>, {\r\n ...;\r\n}>\r\n````\r\n\r\n### Wrong Intellisense\r\n\r\nVsCode popopver hovering `\u003CMyButton />` in the template block of `~/app.vue` (or any other template)\r\n\r\n```TypeScript\r\n(property) 'MyButton': DefineComponent\u003C{}, {}, any>\r\n```\r\n\r\n### Additional context\r\n\r\nThe above example is the current state of the reproduction repo. But a different, but similar behavior happened in other reports (for example a yarn workspace repo). Strange enough, sometimes, it works fine...\r\n\r\n### Logs\r\n\r\n_No response_",[3237,3240,3241,3242],{"name":3238,"color":3239},"types","2875C3",{"name":3193,"color":3194},{"name":3169,"color":3196},{"name":3243,"color":3244},"upstream","E8A36D",21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.7275064,{"description":3251,"labels":3252,"number":3255,"owner":3147,"repository":3148,"state":3184,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Environment\n\n.\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nGo to https://ui3.nuxt.dev/getting-started and change the theme to dark and the neutral color to neutral.\n\n### Description\n\nI just entered the site and had the preference to see the docs with neutral colors and in dark mode and now seems that the last update on the docs brokes the dark mode with neutral color. I tested it in multiple browsers and looks the same.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/f79b85ea-a40a-4f97-9c81-f36735d1eebb\n\n### Logs\n\n```shell-script\n\n```",[3253,3254],{"name":3206,"color":3207},{"name":3141,"color":3142},3399,"Dark mode with neutral color seems to be broken in the v3 UI docs","2025-03-22T15:51:05Z","https://github.com/nuxt/ui/issues/3399",0.7300183,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGyLlXouBfYSFu8ftRBKRB8AXzArhKmBLLXy8bIPdwNo":-1},"/nuxt/ui/4435"]