\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",[1998,2001,2004],{"name":1999,"color":2000},"bug","d73a4a",{"name":2002,"color":2003},"v3","49DCB8",{"name":2005,"color":2006},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.7165806,{"description":2014,"labels":2015,"number":2016,"owner":1988,"repository":2017,"state":1990,"title":2018,"updated_at":2019,"url":2020,"score":2021},"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.7243773,{"description":2023,"labels":2024,"number":2028,"owner":1988,"repository":2029,"state":1990,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### 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_",[2025],{"name":2026,"color":2027},"pending triage","5D08F5",735,"test-utils","No data on Option API component returned by mountSuspended","2025-01-29T17:42:23Z","https://github.com/nuxt/test-utils/issues/735",0.7286693,{"description":2035,"labels":2036,"number":2041,"owner":1988,"repository":2008,"state":1990,"title":2042,"updated_at":2043,"url":2044,"score":2045},"On login page, i have UForm with validation. when clicking on register modal(UModal with #content slot) included Uform with validation, submit button doesn't trigger. if i focus on input, validation works automatically. when clicking submit button after filling all required fields, there are no error on validation(logged in the end of validation function). But no response(also logged in submit function) in submit function. how to fix it? i can't get it?",[2037,2040],{"name":2038,"color":2039},"question","d876e3",{"name":2002,"color":2003},3674,"can't handle submit button","2025-03-25T06:43:01Z","https://github.com/nuxt/ui/issues/3674",0.7290677,{"description":2047,"labels":2048,"number":2049,"owner":1988,"repository":2050,"state":1990,"title":2051,"updated_at":2052,"url":2053,"score":2054},"Hello Nuxters,\r\n\r\nI'm a fan and a supporter of nuxt and wanted to contribute in any way possible.\r\nNot sure if it is under cooking, but if not, I would be glad to add a deploy page for (Coolify.io)[https://coolify.io/]\r\n\r\nPlease let me know if that would be an acceptable pull request.\r\n\r\nThanks,\r\nMohannad",[],1609,"nuxt.com","docs: add deploy to Coolify.io","2024-07-19T06:05:15Z","https://github.com/nuxt/nuxt.com/issues/1609",0.7335652,{"description":2056,"labels":2057,"number":2063,"owner":1988,"repository":2029,"state":2064,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### 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_",[2058,2059,2062],{"name":1999,"color":2000},{"name":2060,"color":2061},"vitest-environment","b60205",{"name":2026,"color":2027},869,"closed","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.6586433,{"description":2070,"labels":2071,"number":2076,"owner":1988,"repository":2077,"state":2064,"title":2078,"updated_at":2079,"url":2080,"score":2081},"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",[2072,2073],{"name":1999,"color":2000},{"name":2074,"color":2075},"pre-announce","c2e0c6",133,"scripts","fix(tpc): a type annotation is necessary","2024-07-15T18:18:26Z","https://github.com/nuxt/scripts/issues/133",0.6682683,{"description":2083,"labels":2084,"number":2091,"owner":1988,"repository":2050,"state":2064,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### 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_",[2085,2088],{"name":2086,"color":2087},"duplicate","cfd3d7",{"name":2089,"color":2090},"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.7196861,{"description":2097,"labels":2098,"number":2016,"owner":1988,"repository":2077,"state":2064,"title":2103,"updated_at":2104,"url":2105,"score":2021},"### 🐛 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_",[2099,2100],{"name":1999,"color":2000},{"name":2101,"color":2102},"upstream","84A80F","Blog: Example does not work after tab switch","2024-09-03T05:51:31Z","https://github.com/nuxt/scripts/issues/212",["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"IcFN1-etzP64VdWvT5_q5C5LMg9FZbFfVpzcDki9hNc":-1},"/nuxt/scripts/393"]