\n \u003C/UChip>\n\u003C/template>\n````\n\n### Description\n\nHey,\n\nThanks for your great work.\n\nI have noticed this on a few elements in UI3, but especaily here padding just is not right. Yes of course you can change it, but i belive there needs to be some sane defaults across all elements.\n\nText in chip, and even a simple number is almost unreadable see screenshot below. Happy to open a pr or list all other elements where this seems to have happened (one that comes to mind is UAvatar https://github.com/nuxt/ui/issues/3558).\n\n\n\n### Additional context\n\nThis example is directly from the UI website",[2010,2011,2014],{"name":1999,"color":2000},{"name":2012,"color":2013},"v3","49DCB8",{"name":2015,"color":2016},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.78418314,{"description":2024,"labels":2025,"number":2029,"owner":1988,"repository":2018,"state":1990,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### Description\n\nHi,\n\nit would be nice to have the option to disable the behaviour that the numbers increase or decrease when the buttons are pressed. Because even if I disable the component it doesn't stops. \n\n```js\n\u003CUInputNumber\n :disabled=\"loadingDec || loadingInc\"\n :min=\"0\"\n :max=\"10\"\n v-model=\"quantity\"\n variant=\"soft\"\n size=\"xl\"\n >\u003Ctemplate #decrement>\n \u003CUButton\n :loading=\"loadingDec\"\n variant=\"link\"\n :icon=\"quantity \u003C= 1 ? 'i-heroicons-trash' : 'i-lucide-minus'\"\n @click=\"loadingDec = true\"\n @mousedown=\"onMousedown()\"\n :ui=\"{\n base: `${iconHoverColor} text-gray-500 disabled:text-gray-500 cursor-pointer`,\n }\"\n />\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_",[2026,2027,2028],{"name":1985,"color":1986},{"name":2012,"color":2013},{"name":2015,"color":2016},3159,"option to disable on press behaviour for increment/decrement for inputNumber component","2025-01-27T08:00:26Z","https://github.com/nuxt/ui/issues/3159",0.7896895,{"description":2035,"labels":2036,"number":2044,"owner":1988,"repository":2002,"state":1990,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### Environment\n\n \"dependencies\": {\r\n \"nuxt\": \"3.12.4\",\r\n \"vue\": \"latest\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/test-utils\": \"3.14.1\",\r\n \"@vue/test-utils\": \"2.4.6\",\r\n \"happy-dom\": \"14.12.3\",\r\n \"jest-image-snapshot\": \"6.4.0\",\r\n \"playwright-core\": \"1.46.0\",\r\n \"vitest\": \"2.0.5\"\r\n }\n\n### Reproduction\n\nDefault.vue\r\n```\r\n\u003Ctemplate>\r\n \u003CNuxtPage />\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\u003C/script>\r\n```\r\n\r\nApp.vue\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>Message: {{ getMessage(\"Hello World\") }}\u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nimport { getMessage } from \"@/service/message-service\";\r\n```\r\n\r\nApp.test.ts\r\n```\r\nimport { it, expect, vi } from \"vitest\";\r\nimport { mountSuspended } from \"@nuxt/test-utils/runtime\";\r\nimport App from \"../../layouts/default.vue\";\r\n\r\nvi.mock(\"@/service/message-service\", () => {\r\n return {\r\n getMessage: () => \"hello from mock!!\",\r\n };\r\n});\r\n\r\n\r\nit(\"nuxt unit testing\", async () => {\r\n const component = await mountSuspended(App, { route: \"/\" });\r\n expect(component.html()).toMatchInlineSnapshot(\r\n `\"\u003Cdiv>Message: hello Hello World\u003C/div>\"`\r\n );\r\n});\r\n\r\n```\r\n\r\nmessage-service.ts\r\n```\r\nexport function getMessage(message: string): string {\r\n console.log(\"FROM ACTUAL\");\r\n return `hell ${message}`;\r\n}\r\n```\r\n\n\n### Describe the bug\n\nI was expecting vitest vi.mock should be able to mock imports to provide custom/mock implementation, however it seems that vi.mock is not working in the context of nuxt test?\r\n\r\nIf so, how are we suppose to create unit tests and/or E2E using nuxt/test-utils package and be able to provide flexible mocking mechanism?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2037,2038,2041],{"name":1999,"color":2000},{"name":2039,"color":2040},"vitest-environment","b60205",{"name":2042,"color":2043},"pending triage","5D08F5",935,"How to mock custom imports while using mountSuspended to test","2024-09-09T02:17:10Z","https://github.com/nuxt/test-utils/issues/935",0.78977895,{"description":2050,"labels":2051,"number":2054,"owner":1988,"repository":2018,"state":1990,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.15.4\nCLI Version: 3.13.2\nNitro Version: 2.10.4\nPackage Manager: npm@11.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n.\n\n### Description\n\nHi\nWhen we use the arrow in the DropdownMenu component, a border is added to the last item. Apparently, this is because the arrow element is added at the end of the items groups in this component.\n\n\n\n\n\nI hope I was able to tell you what I meant. It's nothing special, but it would be great if it could be fixed. 🙄\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2052,2053],{"name":1999,"color":2000},{"name":2012,"color":2013},3315,"arrow causes appear border in the last item of DropdownMenu","2025-02-17T11:48:29Z","https://github.com/nuxt/ui/issues/3315",0.79552513,{"description":2060,"labels":2061,"number":2067,"owner":1988,"repository":2018,"state":2068,"title":2069,"updated_at":2070,"url":2071,"score":2072},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v20.17.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `npm@10.8.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `future`, `devtools`, `runtimeConfig`, `pinia`, `imports`, `modules`, `css`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@vueuse/nuxt@12.8.2`, `@pinia/nuxt@0.10.1`, `@nuxt/image@1.9.0`\n- Build Modules: `-`\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.0\n\n### Reproduction\n\n\n\n### Description\n\n\nOk so I have a little problem... Lucide Icons does not seem to load properly even though i have it installed and cached... I recently installed lucide-vue-next with npm to try and fix this but i still have the same problem occuring.\n\nI noticed that the error seems to be coming from the uselectmenu components i am using...\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2062,2063,2066],{"name":1999,"color":2000},{"name":2064,"color":2065},"needs reproduction","CB47CF",{"name":2012,"color":2013},3494,"closed","Lucide Icons fail to load properly","2025-03-11T16:48:58Z","https://github.com/nuxt/ui/issues/3494",0.7117668,{"description":2074,"labels":2075,"number":2081,"owner":1988,"repository":1988,"state":2068,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Describe the feature\n\nCurrently, the only place where prerendering is started is here:\r\nhttps://github.com/nuxt/nuxt/blob/9742bffac24fbf9fa279d614ad6bf07b5d85672d/packages/nuxt/src/core/nitro.ts#L380C29-L380C29\r\n\r\nIt is therefore not possible to do prerendering from the CLI without also running the build. It would be a great help to my workflow if I could do the build on one server, copy the files, and do the prerendering on another server.\r\n\r\nThere are many use cases for this:\r\n- Retrying the prerendering step without retrying the build step.\r\n- App code did not change, but the routes returned by the `prerender:routes` have changed, and you only want to update the prerendered pages without updating the build and/or without updating previously prerendered routes.\r\n- Splitting build and prerender steps into different CI steps (e.g. Bitbucket Pipelines, where each step is run sequentially in a separate docker container).\r\n- Splitting up large prerender tasks with thousands of routes into independent steps (e.g. copy the build to separate physical machines, run pre-rendering with a different set of routes on each (the `prerender:routes` hook can figure this out based on environment variables) and merge the results afterwards for deployment).\r\n- Workflows where one person is responsible for building, and another for prerendering.\r\n\r\nWhat I would like to see:\r\n- Clear API and CLI to run `build` and `prerender` separately or together.\r\n- `prerender` will obviously fail if results of `build` is missing.\r\n- `build` may throw away results of previous prerendering, but `prerender` should not touch results of previous build.\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2076,2079],{"name":2077,"color":2078},"3.x","29bc7f",{"name":2042,"color":2080},"E99695",22261,"Separate the prerendering step from the build step","2023-07-21T09:39:45Z","https://github.com/nuxt/nuxt/issues/22261",0.758756,{"description":2087,"labels":2088,"number":2089,"owner":1988,"repository":2090,"state":2068,"title":2091,"updated_at":2092,"url":2093,"score":2094},"",[],990,"nuxt.com","[Docs] Add pagination","2023-04-04T08:06:43Z","https://github.com/nuxt/nuxt.com/issues/990",0.75931543,{"description":2096,"labels":2097,"number":2101,"owner":1988,"repository":2018,"state":2068,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### Description\n\nThe [migration](https://ui.nuxt.com/getting-started/migration) page should mention that the old implementation of [DatePicker](https://ui2.nuxt.com/components/date-picker#installation) component is no longer correct as it throw an error on v3.\n\n\n\n### Additional context\n\nNew [DatePicker](https://ui.nuxt.com/components/calendar#as-a-datepicker) implementation is different.",[2098,2099,2100],{"name":1985,"color":1986},{"name":2012,"color":2013},{"name":2015,"color":2016},3557,"`DatePicker` v2 migration guide","2025-03-17T16:17:06Z","https://github.com/nuxt/ui/issues/3557",0.76286256,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"Qlqk1pr913s6PlvK_kSd4H51-Pryd8TWdJC6ES0pA-0":-1},"/nuxt/nuxt.com/1269"]