\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",[2036,2039,2042],{"name":2037,"color":2038},"bug","d73a4a",{"name":2040,"color":2041},"v3","49DCB8",{"name":2043,"color":2044},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.79173464,{"description":2052,"labels":2053,"number":2058,"owner":1985,"repository":1985,"state":2059,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### What problem does this feature solve?\n\nI've tried to use YAML files as data object, followed an example from Next.js https://github.com/zeit/next.js/issues/3141. So if I use something like this\n\n```js\n// pages/index.vue\nimport data from `~static/data.yml`\n\nexport default {\n data () {\n return {\n data\n }\n }\n)\n```\n\nAnd then add yaml loader in nuxt.config.js\n\n```js\nbuild: { \n extend(config, ctx) {\n if (ctx.isDev && ctx.isClient) {\n config.module.rules.push(\n {\n test: /\\.ya?ml$/,\n use: 'js-yaml-loader',\n }\n )\n }\n }\n }\n``` \n\nThis works until I refresh the page. Then I got an error: `Module parse failed: Assigning to rvalue (1:2) You may need an appropriate loader to handle this file type.` And then on next refresh another error: `render function or template not defined in component: anonymous`\n\nAny ideas how to properly use YAML files?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8447\">#c8447\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2054,2055],{"name":1996,"color":1997},{"name":2056,"color":2057},"2.x","d4c5f9",4736,"closed","A way to import YAML as a JavaScript object","2024-12-18T17:34:54Z","https://github.com/nuxt/nuxt/issues/4736",0.7606876,{"description":2065,"labels":2066,"number":2072,"owner":1985,"repository":2073,"state":2059,"title":2074,"updated_at":2075,"url":2076,"score":2077},"due to the listing order being a big influence in traffic for the agency page, would it be possible for the agencies to be presented in a random order when accessing the [Agencies page](https://nuxt.com/support/agencies) ?",[2067,2069],{"name":1996,"color":2068},"1ad6ff",{"name":2070,"color":2071},"marketing","f5c828",1048,"nuxt.com","[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.77041364,{"description":2079,"labels":2080,"number":2081,"owner":1985,"repository":2073,"state":2059,"title":2082,"updated_at":2083,"url":2084,"score":2085},"- Turn Hero into classic one (see /support)\n- Get Started => Reuse block at the end of the page\n- Guide => Stay as is\n- API => Turn into 6 little cards for each section",[],1034,"[Code] Docs landing","2023-09-05T08:18:49Z","https://github.com/nuxt/nuxt.com/issues/1034",0.77574337,{"description":2087,"labels":2088,"number":2081,"owner":1985,"repository":2092,"state":2059,"title":2093,"updated_at":2094,"url":2095,"score":2085},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: ../../packages/package-one/src/module, ../../packages/package-two/src/module\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nYou get the error when using vitest 2.1.8 (the error appears since 2.1.5): https://stackblitz.com/edit/github-n797ja-hxhseq\n\nIt works in 2.1.4: https://stackblitz.com/edit/github-n797ja-2rtuvw\n\n### Describe the bug\n\nIn a workspace with multiple projects, it is no longer possible to call defineVitestConfig because of unctx conflicts:\n\n```\nError: Context conflict\n at checkConflict (file:///home/projects/github-n797ja-hxhseq/node_modules/unctx/dist/index.mjs:25:13)\n at set (file:///home/projects/github-n797ja-hxhseq/node_modules/unctx/dist/index.mjs:59:22)\n at initNuxt (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4404:21)\n at ready (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4306:26)\n at loadNuxt (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4871:16)\n```\n\nCould be related to https://github.com/nuxt/test-utils/issues/537\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2089],{"name":2090,"color":2091},"pending triage","5D08F5","test-utils","Can't load config files in workspace since vitest 2.1.5","2025-02-11T15:38:57Z","https://github.com/nuxt/test-utils/issues/1034",{"description":2097,"labels":2098,"number":2099,"owner":1985,"repository":2013,"state":2059,"title":2100,"updated_at":2101,"url":2102,"score":2103},"Now that TailwindCSS v4 is going stable, we should better support it.\n\n- [x] **Playground**: Add TailwindCSS v4 example. It'd be ideal if we can find a way to keep v3 and v4 in one npm project.\n- [x] **Test**: Test for TailwindCSS v4\n- [ ] Auto enable `experimental.processCSSVariables` if Tailwind v4 is detected (i.e. `@tailwindcss/vite` is installed)",[],468,"TailwindCSS v4","2025-03-10T13:13:24Z","https://github.com/nuxt/fonts/issues/468",0.7815781,["Reactive",2105],{},["Set"],["ShallowReactive",2108],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"MvUn_kdfhCeRugPYak62T2r_PNqXnmPiXhkX0_2OGeE":-1},"/nuxt/icon/89"]