\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",[2938,2939,2940],{"name":2907,"color":2908},{"name":2910,"color":2911},{"name":2913,"color":2914},3633,"Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.738026,{"description":2947,"labels":2948,"number":2949,"owner":2916,"repository":2950,"state":2918,"title":2951,"updated_at":2952,"url":2953,"score":2954},"Usually I fetched the different icons with something like.\r\n```\r\nvar icons = import.meta.glob(`.././assets/*.svg`, { as: \"raw\", eager: true })\r\n\r\nfor (const item in icons) {\r\n body.innerHTML = icons[item]\r\n let name = item.formatx(`../assets/$V.svg`)\r\n let color = body.querySelector(\"#color\")?.getAttributeNS(null, \"fill\") || \"black\"\r\n let size = undefined // TODO\r\n\r\n result.push(await icon(`${name} c-${color}`, body.querySelector(\"svg\") || undefined))\r\n}\r\n```\r\n\r\nBut this returns\r\n\r\n\r\nIs there a better way?",[],222,"icon","How to list all available custom icons","2025-02-23T21:51:46Z","https://github.com/nuxt/icon/issues/222",0.7448008,{"description":2956,"labels":2957,"number":2958,"owner":2916,"repository":2959,"state":2960,"title":2961,"updated_at":2962,"url":2963,"score":2964},"This plugin should be registered in `ProjectContentEditor.vue`\n\nhttps://discuss.prosemirror.net/t/collab-with-socket-io-and-vue-how-to-apply-changes-back-to-editor-view/2640\n\nhttps://github.com/Saul-Mirone/milkdown/blob/main/packages/plugin-collaborative/src/index.ts",[],385,"nuxt.com","closed","Collaborative plugin","2023-06-06T12:14:51Z","https://github.com/nuxt/nuxt.com/issues/385",0.7072114,{"description":2966,"labels":2967,"number":2958,"owner":2916,"repository":2971,"state":2960,"title":2972,"updated_at":2973,"url":2974,"score":2964},"### 📚 Is your documentation request related to a problem?\n\nI simply added the nuxt/script and enabled google tag manager. Locally all tests run fine however when running tests upon deploy (through sonarqube upon PR changes).\n\nThe test succeeds but there are errors on top of it causing this to fail the step. There are multiple errors which I can't reproduce locally.\n\n- Failed to parse URL from //tr.outbrain.com/unifiedPixel?....\n- NetworkError: Fetch to \"https://f.clarity.ms/collect\" failed. Error: The operation was aborted.\n- NetworkError: Fetch to \"https://analytics.tiktok.com/api/v2/pixel/act\" failed. Error: The operation was aborted.\n- NetworkError: Cross-Origin Request Blocked: The Same Origin Policy dissallows reading the remote resource at \"https://f.clarity.ms/collect\".\n\nMainly parse URL errors. However this isn't all that relevant for my testing so I was wondering if there happens to be a way to maybe disable this behaviour whilst testing?\n\n### 🔍 Where should you find it?\n\nVitest / Testing (non-existent yet?)\n\n### ℹ️ Additional context\n\n_No response_",[2968],{"name":2969,"color":2970},"documentation","0075ca","scripts","Vitest combined with GTM","2025-02-12T09:08:53Z","https://github.com/nuxt/scripts/issues/385",{"description":2976,"labels":2977,"number":2980,"owner":2916,"repository":2959,"state":2960,"title":2981,"updated_at":2982,"url":2983,"score":2984},"After updating the API, Jobs page is on error under certain circumstances : \n\nRelated commit : https://github.com/nuxtlabs/nuxt.com/commit/8962705b5d0dda99724d661efeeb4ed18e332db4\n\nEnvironment (Preview) : https://framework-p2aadzhns-nuxt-js.vercel.app/\n\n```\nTypeError: Cannot read properties of undefined (reading 'map')\n```\n\nThis is due to changes in the data structure of the API, changing from `\u003CNuxtJob[]>` to `{ data: \u003CNuxtJob[]>`. API endpoint (/api/jobs) seems to sometimes serve the outdated data.\n\n- 1 : client-side navigation from / to /support/jobs : fails\n- 2 : Server hit on /support/jobs : works\n- 3: client-side navigation back and forth to /support/jobs after 2 : works",[2978],{"name":2907,"color":2979},"ff281a",1041,"[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7175906,{"description":2986,"labels":2987,"number":2990,"owner":2916,"repository":2959,"state":2960,"title":2991,"updated_at":2992,"url":2993,"score":2994}," \n\n- [ ] No empty state for repositories, i put an example there nuxtlabs/nuxt.com#613\n\n\n- [x] Padding up & down the border should be 16px instead of 12px\n\n\n- [x] Icon should be 18px and space between icon & text should be 8px\n\n\n- [x] icon should be 20px and space between text & icon should also be 8px + underline should be only on text (width: calc(100% - 20px); right: 0;) and 4px below the actual position of it\n\n\n- [x] [Tablet] You can make 2 cols in tablet\n\n\n- [x] [Tablet] You can reduce image opacity like you do in mobile for tablet resolutions\n\n\n- [ ] [Mobile] Selects should be width full (in very small resolutions) nuxtlabs/nuxt.com#612\n\n**Idea**\n- [ ] [Mobile] Maybe adding a back to top on mobile because scroll can be very long\n\n\n- [x] [Darkmode] Repo title should be white\n\n\n- [x] Increase the space between Title & Description by 4px\n\n",[2988],{"name":2927,"color":2989},"1ad6ff",609,"[Resources] Repositories improvements V2","2022-06-14T10:46:20Z","https://github.com/nuxt/nuxt.com/issues/609",0.72694635,{"description":2996,"labels":2997,"number":2990,"owner":2916,"repository":3001,"state":2960,"title":3002,"updated_at":3003,"url":3004,"score":2994},"When testing a composable that uses useAsyncData, errors get re-instantiated as the default Error class. This creates problems when testing code that acts on specific error instance types.\r\n\r\nI expect error instances to be used the way they are passed to the `mockResolvedValue` function.\r\n\r\nReproduction stackblitz: https://stackblitz.com/edit/nuxt-starter-69sxkx?file=composables%2FuseData.spec.ts\r\n\r\nRun `npm run test` to see the problem.",[2998],{"name":2999,"color":3000},"vitest-environment","b60205","test-utils","Rejected errors in useAsyncData are broken","2023-12-02T23:30:22Z","https://github.com/nuxt/test-utils/issues/609",{"description":3006,"labels":3007,"number":3011,"owner":2916,"repository":2959,"state":2960,"title":3012,"updated_at":3013,"url":3014,"score":3015},"",[3008],{"name":3009,"color":3010},"design","00bd6f",1019,"[Code] /docs/examples","2022-11-18T14:52:14Z","https://github.com/nuxt/nuxt.com/issues/1019",0.7299655,["Reactive",3017],{},["Set"],["ShallowReactive",3020],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fAguqq1ir4Whz9nIxcAOPK7OAJEi7c0zA4nOKcu2STIk":-1},"/nuxt/icon/368"]