\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",[2015,2018,2021],{"name":2016,"color":2017},"bug","d73a4a",{"name":2019,"color":2020},"v3","49DCB8",{"name":2022,"color":2023},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.7754432,{"description":2031,"labels":2032,"number":2034,"owner":1988,"repository":2035,"state":1990,"title":2036,"updated_at":2037,"url":2038,"score":2039},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[2033],{"name":2016,"color":2017},684,"test-utils","mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.7761452,{"description":2041,"labels":2042,"number":2046,"owner":1988,"repository":2035,"state":1990,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ddvycp\r\n\r\n### Describe the bug\r\n\r\n```ts\r\nconst wrapper = await mountSuspended(OptionAPIComponent)\r\n```\r\n`wrapper.vm.$data` is empty\r\n`wrapper.setData({...data})` will result into error:\r\n```\r\nTypeError: Cannot add property, object is not extensible\r\n```\r\n\r\nFurthermore, I cannot call any method of the component instance:\r\n```\r\nTypeError: wrapper.vm.myMethod is not a function\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nComponent written in composition api doesn't have this issue.\r\n@vue/test-utils doesn't have this issue.\r\n\r\n### Logs\r\n\r\n_No response_",[2043],{"name":2044,"color":2045},"pending triage","5D08F5",735,"No data on Option API component returned by mountSuspended","2025-01-29T17:42:23Z","https://github.com/nuxt/test-utils/issues/735",0.7767645,{"description":2052,"labels":2053,"number":2054,"owner":1988,"repository":1989,"state":2055,"title":2056,"updated_at":2057,"url":2058,"score":2059},"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,"closed","Adding fonts like \"Quiksand\" and \"Urbanist\" fails","2024-10-13T07:26:25Z","https://github.com/nuxt/fonts/issues/239",0.72886044,{"description":2061,"labels":2062,"number":2063,"owner":1988,"repository":1999,"state":2055,"title":2064,"updated_at":2065,"url":2066,"score":2067},"This Warn appears when some other modules uses component with name \"Icon\" (for ex with @iconify or @nuxt/ui)\r\n\r\n\" WARN Overriding Icon component. You can specify a priority option when calling addComponent to avoid this warning. \"\r\n\r\nI supposed it happens somewhere inside nuxt's autoimports behind the scene. Even if i don't use any NuxtUi icons anywhere.\r\nIf i comment @nuxt/icon (or @nuxt/ui) module in nuxt.config.ts - problem dissapears\r\n\r\nProbably for @nuxt/icon would need some prefix or ability to make some prefix when there are several modules with Icon components\r\n\r\nand other thing - this warning doesn't give understanding what should i do exactly ) where i need to \"specify a priority option\" cuz i don't \"calling addComponent\" anywhere directly ))) more questions and no answers )\r\n",[],200,"@nuxt/icon conflicting with @nuxt/ui (and probably with others UI framework which uses \"Icon\" component)","2024-07-18T22:45:12Z","https://github.com/nuxt/icon/issues/200",0.7355393,{"description":2069,"labels":2070,"number":1987,"owner":1988,"repository":1999,"state":2055,"title":2071,"updated_at":2072,"url":2073,"score":1994},"Hi\r\n\r\nI would like to know if some contributors might be interested in a change of the api. I would be happy to help.\r\n\r\nThe idea is to load icons from an SVG folder inside the assets folder.\r\nTo achieve this, there is a need to implement an npm command, such as `npm run icon:prepare`, that will download the used icons from Iconify during the deployment script or before pushing to the git repository.\r\n\r\n- The icons will be downloaded in `@/assets/svg/[name of the collection]/[name of the icon].svg`\r\n- Additionally move the custom icons from `@/components/global` to `@/assets/svg/custom`\r\n\r\n### The main advantages are:\r\n- No need to rely on iconify API\r\n- Ability to include the icons in server-side rendering\r\n- Improved performance\r\n- Ability to change/customize the icons's SVG locally if needed\r\n- Disable cache in the local storage from Iconify",[],"[Feature Request]: SVG folder for offline mode and custom SVGs","2024-05-02T07:15:59Z","https://github.com/nuxt/icon/issues/131",{"description":2075,"labels":2076,"number":1998,"owner":1988,"repository":2081,"state":2055,"title":2082,"updated_at":2083,"url":2084,"score":2003},"### 🐛 The bug\r\n\r\nAlso shown in the video below from 00:06 on (before just a sanity check that it works).\r\n\r\n1. Go to https://nuxt.com/blog/nuxt-scripts\r\n2. Scroll to the YouTube example\r\n3. DO NOT click the video yet\r\n4. Click on \"input\"\r\n5. Click on \"output\" again\r\n6. Try to play the video\r\n7. See that it doesn't work\r\n\r\n\r\n[nuxt-blog-scripts.webm](https://github.com/user-attachments/assets/d92655a4-6c95-495d-b33c-35797a180e7e)\r\n\r\n\r\n### 🛠️ To reproduce\r\n\r\nhttps://nuxt.com/blog/nuxt-scripts\r\n\r\n### 🌈 Expected behavior\r\n\r\nThe video should be loaded after the click too\r\n\r\n### ℹ️ Additional context\r\n\r\n_No response_",[2077,2078],{"name":2016,"color":2017},{"name":2079,"color":2080},"upstream","84A80F","scripts","Blog: Example does not work after tab switch","2024-09-03T05:51:31Z","https://github.com/nuxt/scripts/issues/212",["Reactive",2086],{},["Set"],["ShallowReactive",2089],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"ggV8npb54ObBelcoCi-WeJs9obEAv5WSKJjszdWM7IA":-1},"/nuxt/icon/271"]