\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",[1984,1987,1990],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3633,"nuxt","ui","open","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.70107275,{"description":2002,"labels":2003,"number":2007,"owner":1994,"repository":2008,"state":1996,"title":2009,"updated_at":2010,"url":2011,"score":2012},"From my testings, only weights `400` (normal) and `700` (bold) are available out of the box by using the `@nuxtjs/tailwindcss` module like this:\r\n\r\n```html\r\n\u003Cspan class=\"font-roboto\">...\u003C/span> \u003C!-- Works -->\r\n\r\n\u003Cspan class=\"font-roboto font-bold\">...\u003C/span> \u003C!-- Works -->\r\n\r\n\u003Cspan class=\"font-roboto font-medium\">...\u003C/span> \u003C!-- Doesn't work -->\r\n```\r\n\r\n> `font-roboto` is defined in tailwind.config.\r\n\r\nAm I missing something, or do I do have to specify the other weights in the module options?",[2004],{"name":2005,"color":2006},"enhancement","a2eeef",209,"fonts","detect font weights automatically","2024-11-24T15:36:51Z","https://github.com/nuxt/fonts/issues/209",0.724393,{"description":2014,"labels":2015,"number":2020,"owner":1994,"repository":1995,"state":1996,"title":2021,"updated_at":2022,"url":2023,"score":2024},"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?",[2016,2019],{"name":2017,"color":2018},"question","d876e3",{"name":1988,"color":1989},3674,"can't handle submit button","2025-03-25T06:43:01Z","https://github.com/nuxt/ui/issues/3674",0.7274845,{"description":2026,"labels":2027,"number":2029,"owner":1994,"repository":2030,"state":1996,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### 🆒 Your use case\n\nSo far I have been using Cloudflare Zaraz which collects data on the server side.\r\n\r\nSuch data collection is independent of blockers and cookies and other elements. Thanks to this, statistics are more stable and are usually not affected by the browser quite strongly.\r\n\r\nI have noticed a really huge problem and a huge drop in views and stability of data collection when moving GA4 from Cloudflare Zaraz to Nuxt Scripts.\r\n\r\nIt would be great if in the future there was a possibility of collecting data using server-side as it is described for example here:\r\n\r\nhttps://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics\r\n\r\nFor now, unfortunately, I am returning to Cloudflare Zaraz with most scripts because then everything is more stable and less blocked.\n\n### 🆕 The solution you'd like\n\nhttps://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics\n\n### 🔍 Alternatives you've considered\n\n_No response_\n\n### ℹ️ Additional info\n\n_No response_",[2028],{"name":2005,"color":2006},238,"scripts","Server side GA4","2024-09-03T13:45:06Z","https://github.com/nuxt/scripts/issues/238",0.72933024,{"description":2036,"labels":2037,"number":2042,"owner":1994,"repository":2030,"state":2043,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### 🐛 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_",[2038,2039],{"name":1985,"color":1986},{"name":2040,"color":2041},"upstream","84A80F",212,"closed","Blog: Example does not work after tab switch","2024-09-03T05:51:31Z","https://github.com/nuxt/scripts/issues/212",0.44933492,{"description":2049,"labels":2050,"number":2055,"owner":1994,"repository":2030,"state":2043,"title":2056,"updated_at":2057,"url":2058,"score":2059},"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",[2051,2052],{"name":1985,"color":1986},{"name":2053,"color":2054},"pre-announce","c2e0c6",133,"fix(tpc): a type annotation is necessary","2024-07-15T18:18:26Z","https://github.com/nuxt/scripts/issues/133",0.6040079,{"description":2061,"labels":2062,"number":2066,"owner":1994,"repository":2008,"state":2043,"title":2067,"updated_at":2068,"url":2069,"score":2070},"We've stumbled on an issue, Roboto font was registered in Font Book, so only Safari loaded the font on the browser properly. All other browsers (Chrome, Firefox) fell back to Arial. ",[2063],{"name":2064,"color":2065},"needs reproduction","C94E53",64,"Font is not loading if the same font is registered in Font Book.","2024-03-20T13:28:13Z","https://github.com/nuxt/fonts/issues/64",0.675186,{"description":2072,"labels":2073,"number":2079,"owner":1994,"repository":2080,"state":2043,"title":2081,"updated_at":2082,"url":2083,"score":2084},"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) ?",[2074,2076],{"name":2005,"color":2075},"1ad6ff",{"name":2077,"color":2078},"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.67898047,{"description":2086,"labels":2087,"number":2094,"owner":1994,"repository":2080,"state":2043,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### 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_",[2088,2091],{"name":2089,"color":2090},"duplicate","cfd3d7",{"name":2092,"color":2093},"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.7010376,{"description":2100,"labels":2101,"number":2109,"owner":1994,"repository":2110,"state":2043,"title":2111,"updated_at":2112,"url":2113,"score":2114},"### 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_",[2102,2103,2106],{"name":1985,"color":1986},{"name":2104,"color":2105},"vitest-environment","b60205",{"name":2107,"color":2108},"pending triage","5D08F5",869,"test-utils","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.71123266,["Reactive",2116],{},["Set"],["ShallowReactive",2119],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"yXsf4v6zmjXNBtoeCNUTsjH2lJcRLuHNEclf9Rsnk6s":-1},"/nuxt/icon/212"]