\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",[3018,3021,3024],{"name":3019,"color":3020},"bug","d73a4a",{"name":3022,"color":3023},"v3","49DCB8",{"name":3025,"color":3026},"triage","ffffff",3633,"nuxt","ui","open","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.67769563,{"description":3036,"labels":3037,"number":3038,"owner":3028,"repository":3039,"state":3030,"title":3040,"updated_at":3041,"url":3042,"score":3043},"I added @nuxt/icon to my project. In the project it is working fine but in histoire it is not working.\r\nIn histoire it is not able to render the stories that contain components that use @nuxt/icon.\r\n\r\nOn devtools console you always see the error:\r\n\u003Cimg width=\"654\" alt=\"Bildschirmfoto 2024-07-22 um 21 10 24\" src=\"https://github.com/user-attachments/assets/4793e76d-e549-4712-bdfc-dc230c1cb56f\">\r\n\r\nit doesn't matter if mode is css or svg, it doesn't matter if from iconify icon libs, global components or custom collections, it is simple not able to work with it. The error is always the same.\r\n\r\nHere is a reproduction: https://stackblitz.com/edit/nuxt-starter-kckxy8\r\nrun the histoire to see the story not getting rendered and the console error in devtools.\r\n\r\nPlease help!",[],212,"icon","@nuxt/icon not working in histoire with mode \"svg\"","2024-08-11T05:45:02Z","https://github.com/nuxt/icon/issues/212",0.7067161,{"description":3045,"labels":3046,"number":3048,"owner":3028,"repository":3049,"state":3030,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### 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",[3047],{"name":3019,"color":3020},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.7492206,{"description":3055,"labels":3056,"number":3057,"owner":3028,"repository":3039,"state":3030,"title":3058,"updated_at":3059,"url":3060,"score":3061},"https://stackblitz.com/edit/nuxt-icon-playground-frxmrw4y\n\nIcons not displayed",[],368,"Not shows with new Nuxt 3.16.0","2025-03-13T12:52:04Z","https://github.com/nuxt/icon/issues/368",0.75098056,{"description":3063,"labels":3064,"number":3069,"owner":3028,"repository":3070,"state":3071,"title":3072,"updated_at":3073,"url":3074,"score":3075},"Upgrading to v6.0.2 I get the following errors in the Nuxt Turnstile module:\r\n\r\n```\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleTagManager' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleAnalytics' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n```\r\n\r\nhttps://github.com/nuxt-modules/turnstile/actions/runs/9820960416/job/27116095724?pr=321#step:14:24",[3065,3066],{"name":3019,"color":3020},{"name":3067,"color":3068},"pre-announce","c2e0c6",133,"scripts","closed","fix(tpc): a type annotation is necessary","2024-07-15T18:18:26Z","https://github.com/nuxt/scripts/issues/133",0.6812168,{"description":3077,"labels":3078,"number":3086,"owner":3028,"repository":3049,"state":3071,"title":3087,"updated_at":3088,"url":3089,"score":3090},"### Environment\n\nWorking directory: /home/projects/github-h9agvz\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, srcDir\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-h9agvz?file=vitest.config.ts,nuxt.config.ts\n\n### Describe the bug\n\nThe coverage report (by either v8 or istanbul) does not get generated if I change the `srcDir` configuration in `nuxt.config.js`. It seems it works well if I use the default setting. You can reproduce the issue with the link I provided.\r\n\r\nIf I click on the *Coverage* icon button on `vitest-ui` web page, It shows the error text: `Cannot GET /coverage/index.html`.\r\n\r\nIf I run `vitest` with `--ui` and `coverage.enabled` option to `true` then the coverage report's `html` files should be generated in `/coverage` directory, but what I get is only `tmp` directory with `coverage.json` files included. It seems the `.html` files are not generated properly so that the output directory get empty.\r\n\r\nI even tried to change `reportsDirectory` or `root` in `vitest.config.js` but nothing changes.\n\n### Additional context\n\nSometimes if I run `vitest --ui` then after the preparation is ready, the open browser should show the Vitest UI, but it shows `Cannot GET /`. After that if I click the URL printed on the console (UI started at http://localhost:51204/__vitest__/), then it goes to the UI page. Also, if I click the *Coverage* icon on that page, it shows the error text of `Cannot GET /coverage/index.html` as well.\n\n### Logs\n\n_No response_",[3079,3080,3083],{"name":3019,"color":3020},{"name":3081,"color":3082},"vitest-environment","b60205",{"name":3084,"color":3085},"pending triage","5D08F5",869,"Coverage report does not get generated if `srcDir` in `nuxt.config.js` is modified.","2024-09-30T14:25:26Z","https://github.com/nuxt/test-utils/issues/869",0.69382197,{"description":3092,"labels":3093,"number":3038,"owner":3028,"repository":3070,"state":3071,"title":3098,"updated_at":3099,"url":3100,"score":3043},"### 🐛 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_",[3094,3095],{"name":3019,"color":3020},{"name":3096,"color":3097},"upstream","84A80F","Blog: Example does not work after tab switch","2024-09-03T05:51:31Z","https://github.com/nuxt/scripts/issues/212",{"description":3102,"labels":3103,"number":3107,"owner":3028,"repository":3108,"state":3071,"title":3109,"updated_at":3110,"url":3111,"score":3112},"Add the possibility to flag the websites done by our agency partners.\n--> a category to sort by on the left\n--> a tag on the site thumbnail on the showcase page",[3104],{"name":3105,"color":3106},"enhancement","1ad6ff",813,"nuxt.com","Add a tag \"partner\" to websites in the Showcase","2023-10-04T09:26:46Z","https://github.com/nuxt/nuxt.com/issues/813",0.71439266,{"description":3114,"labels":3115,"number":3118,"owner":3028,"repository":3108,"state":3071,"title":3119,"updated_at":3120,"url":3121,"score":3122},"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",[3116],{"name":3019,"color":3117},"ff281a",1041,"[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7174266,{"description":3124,"labels":3125,"number":3131,"owner":3028,"repository":3029,"state":3071,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.7.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun\n- Builder: -\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.12\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha12\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/hidden-snow-d6s8wz?workspaceId=ws_JNWrpb8H73oZGFCJNwBaqL\n\n### Description\n\nWhen using the USelectMenu within a UModal, the search input of the select menu is not working correctly.\n\nIt can't be focused and typing only focuses the SelectMenu itself.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3126,3127,3130],{"name":3019,"color":3020},{"name":3128,"color":3129},"duplicate","cfd3d7",{"name":3022,"color":3023},3288,"USelectMenu broken within UModal","2025-02-11T14:11:07Z","https://github.com/nuxt/ui/issues/3288",0.7211303,["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fa-H97-_xD1GEZEDwP6ZNTpYIrybc0azyp3WkFhDPoZc":-1},"/nuxt/nuxt.com/1400"]