\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",[3045,3046,3049],{"name":3020,"color":3021},{"name":3047,"color":3048},"v3","49DCB8",{"name":3050,"color":3051},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.78582674,{"description":3059,"labels":3060,"number":3066,"owner":3023,"repository":3053,"state":3067,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### 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```",[3061,3062,3065],{"name":3020,"color":3021},{"name":3063,"color":3064},"needs reproduction","CB47CF",{"name":3047,"color":3048},3494,"closed","Lucide Icons fail to load properly","2025-03-11T16:48:58Z","https://github.com/nuxt/ui/issues/3494",0.724117,{"description":3073,"labels":3074,"number":3077,"owner":3023,"repository":3078,"state":3067,"title":3079,"updated_at":3080,"url":3081,"score":3082},"",[3075],{"name":3020,"color":3076},"ff281a",282,"nuxt.com","After publish, default_branch must be selected","2023-02-15T12:31:21Z","https://github.com/nuxt/nuxt.com/issues/282",0.76310116,{"description":3084,"labels":3085,"number":3077,"owner":3023,"repository":3024,"state":3067,"title":3092,"updated_at":3093,"url":3094,"score":3082},"\r\nWhen you click 'Setup' navigation link nothing happend. 'Setup' tab on the left also does not get highlighted.\r\n\r\n",[3086,3089],{"name":3087,"color":3088},"documentation","0075ca",{"name":3090,"color":3091},"v0","4137F6","Documentation. Page api-reference/setup/ suggests navigate to herself","2024-05-01T16:04:38Z","https://github.com/nuxt/test-utils/issues/282",{"description":3096,"labels":3097,"number":3101,"owner":3023,"repository":3053,"state":3067,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### 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.",[3098,3099,3100],{"name":3034,"color":3035},{"name":3047,"color":3048},{"name":3050,"color":3051},3557,"`DatePicker` v2 migration guide","2025-03-17T16:17:06Z","https://github.com/nuxt/ui/issues/3557",0.7639379,{"description":3107,"labels":3108,"number":3115,"owner":3023,"repository":3078,"state":3067,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\r\n\r\nFirefox Browser on Windows\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nText is aggressively wrapped in `\u003Ccode>` blocks inside a table, so the Lifecycle Hooks page is difficult to read.\r\n\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_",[3109,3112],{"name":3110,"color":3111},"duplicate","cfd3d7",{"name":3113,"color":3114},"responsive","1cd1c6",1400,"Documentation Lifecycle Hooks code blocks is aggresively wrapped","2023-12-08T15:49:41Z","https://github.com/nuxt/nuxt.com/issues/1400",0.7661954,{"description":3121,"labels":3122,"number":3129,"owner":3023,"repository":3023,"state":3067,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### 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).",[3123,3126],{"name":3124,"color":3125},"3.x","29bc7f",{"name":3127,"color":3128},"pending triage","E99695",22261,"Separate the prerendering step from the build step","2023-07-21T09:39:45Z","https://github.com/nuxt/nuxt/issues/22261",0.7686564,{"description":3135,"labels":3136,"number":3137,"owner":3023,"repository":3037,"state":3067,"title":3138,"updated_at":3139,"url":3140,"score":3141},"Fonts like \"Quiksand\" and \"Urbanist\" failing in deployed project.\r\nBut \"Poppins\" it adds correctly.\r\n\r\nI was happy to easily can choose so much fonts in local development but in deployed project it fails.\r\nHoping it will be fixed soon....",[],239,"Adding fonts like \"Quiksand\" and \"Urbanist\" fails","2024-10-13T07:26:25Z","https://github.com/nuxt/fonts/issues/239",0.7688421,["Reactive",3143],{},["Set"],["ShallowReactive",3146],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQlqk1pr913s6PlvK_kSd4H51-Pryd8TWdJC6ES0pA-0":-1},"/nuxt/nuxt.com/1269"]