\n\u003C/template>\n```\n\nThis is working when loading the page SSR, but navigating to the page results in errors like this:\n`DR5f3n0Z.js:52 [Icon] failed to load icon 'twemoji:flag-hungary'`\n\nHow can I create the icon names dynamically?",[1984],{"name":1985,"color":1986},"need-repro","A50BA3",321,"nuxt","icon","open","Dynamic icon name","2024-12-12T08:54:20Z","https://github.com/nuxt/icon/issues/321",0.7689941,{"description":1996,"labels":1997,"number":2001,"owner":1988,"repository":2002,"state":2003,"title":2004,"updated_at":2005,"url":2006,"score":2007},"**Something like:**\r\n\r\n**Inspired by**\r\nhttps://github.com/aaron-bond/better-comments\r\n\r\n",[1998],{"name":1999,"color":2000},"vitest-environment","b60205",511,"test-utils","closed","Add support for generating tests by comment","2023-12-02T00:27:09Z","https://github.com/nuxt/test-utils/issues/511",0.46119916,{"description":2009,"labels":2010,"number":2014,"owner":1988,"repository":2015,"state":2003,"title":2016,"updated_at":2017,"url":2018,"score":2019},"Here are some small ajustments we can do to make the page look even better\n\n\n- [ ] Imo, those social links should open in target blank (and maybe display an external icon on top-right to show you're leaving the site)\n\n\n____\n\n- [ ] Add space between title and testimonials, and make the author stick to the end of text, it will look better and easier to understand\n\n\n____\n\n- [ ] On this illustration i bet we can remove the \"document\" icon, as it is so small it pixelates\n\n\nWDTY guys ? @SarahM19 @Atinux @clemcode @Flosciante \n\nOtherwise, insane job, well done :mountain:",[2011],{"name":2012,"color":2013},"enhancement","1ad6ff",982,"nuxt.com","[Home] [Suggestion] Landing page UI improvements","2023-02-01T09:15:06Z","https://github.com/nuxt/nuxt.com/issues/982",0.71773493,{"description":2021,"labels":2022,"number":2024,"owner":1988,"repository":2002,"state":2003,"title":2025,"updated_at":2026,"url":2027,"score":2028},"It seems after upgrading to 0.7.0 with vitest 0.31 I receive the error:\r\n```\r\nError while requiring module `vitest-environment-nuxt/module`: Error: Cannot find module 'vitest-environment-nuxt/module'\r\n```\r\n\r\nWhich looks like it is trying to be installed by the module required for this package.\r\n\r\nStrange though as I see `vitest-environment-nuxt` as a dependency in the package.json\r\n\r\nIt could be @nuxt/test-utils > vitest conflicting versions. I'll do some digging.",[2023],{"name":1999,"color":2000},584,"Bug: v0.7.0 - Error while requiring module `vitest-environment-nuxt/module`: Error: Cannot find module 'vitest-environment-nuxt/module'","2023-12-02T00:37:12Z","https://github.com/nuxt/test-utils/issues/584",0.72278774,{"description":2030,"labels":2031,"number":2033,"owner":1988,"repository":2002,"state":2003,"title":2034,"updated_at":2035,"url":2036,"score":2037},"I'm testing a page. And inside the unit test I'd like to access the setup state, so I can execute the `onSuccess` function.\r\nIt is possible but it seems a bit cumbersome, I understand I have to find the component because it's wrapped.\r\n\r\n```js\r\n\u003Ctemplate>\r\n \u003Cdiv>Example\u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup type=\"ts\">\r\nconst { data } = await useDetailData();\r\n\r\nfunction onSuccess() {\r\n window.dispatchEvent(new CustomEvent('success'));\r\n\u003C/script>\r\n```\r\n\r\nThis a unit test, as you can see it's difficult to access the setupState of the wrapped Componened passed to mountSuspended.\r\nOr is this already possible somehow? Else I'd be able to make a PR to expose the setupState for easier access.\r\n\r\n```js\r\nit('should dispatch success event', async () => {\r\n const wrapper = await mountSuspended(DetailPage); // name of file is [...slug].vue\r\n\r\n const spy = vi.spyOn(window, 'dispatchEvent');\r\n // this works\r\n const detailPageWrapper = wrapper.findComponent({ name: '[...slug]'}).componentVM._.setupState;\r\n \r\n // But i'd prefer to use something like this instead: \r\n const detailPageWrapper = wrapper.findComponent({ name: '[...slug]'}).vm\r\n // Or this\r\n wrapper.setupState.onSuccess();\r\n\r\n \r\n detailPageWrapper.onSuccess();\r\n\r\n expect(spy).toHaveBeenCalledWith(\r\n expect.objectContaining({ type: 'success' })\r\n );\r\n});\r\n",[2032],{"name":1999,"color":2000},616,"[mountSuspended] Easier access to setupState","2023-12-02T17:18:48Z","https://github.com/nuxt/test-utils/issues/616",0.72454244,{"description":2039,"labels":2040,"number":2041,"owner":1988,"repository":1989,"state":2003,"title":2042,"updated_at":2043,"url":2044,"score":2045},"I'm using @nuxt/icon as part of @nuxt/ui, but I don't think, this makes a difference.\n\nWhat I'm doing/I'd like to do:\n- I reference the icon `mdi:cog`. It's displayed nicely in the current text color, switching light/dark mode.\n- I take the SVG code that is used in the rendered HTML. (I want to slightly modify it, but I'm not doing it just to demonstrate the issue.) I put the SVG coder into a `cog.svg` in my custom icons folder.\n- I reference it with `custom:cog`.\n\nWhat I'm expecting:\n- Both icons should behave exactly the same with respect to size/color/...\n\nWhat actually happens:\n- While the `mdi:cog` icon has text color and switches when changing dark/light mode, the `custom:cog` icon is always displayed in black.\n\nWhen looking at the rendered HTML/CSS it looks very different for custom icon than for the non-custom icon:\nWhile the `mdi:cog` uses the css propery `mask-image`, the `custom:cog` uses `background-image´.\n\nIt would be very cool to either change this behavior so that custom icons behave like regular icons or at least document the difference.",[],324,"Custom icon gets rendered differently (mask-image vs. background-image)","2024-12-18T09:49:35Z","https://github.com/nuxt/icon/issues/324",0.7259266,{"description":2047,"labels":2048,"number":2058,"owner":1988,"repository":2059,"state":2003,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Description\n\nSidebar has an inline style of `width: 15%`. I want to override that and control it's width from tailwindcss classes. I have tried providing a style attribute but it does not seem to work.",[2049,2052,2055],{"name":2050,"color":2051},"question","d876e3",{"name":2053,"color":2054},"v3","49DCB8",{"name":2056,"color":2057},"pro","5BD3CB",3476,"ui","Control the width of sidebar","2025-03-19T18:00:11Z","https://github.com/nuxt/ui/issues/3476",0.7267676,{"description":2065,"labels":2066,"number":2071,"owner":1988,"repository":2059,"state":2003,"title":2072,"updated_at":2073,"url":2074,"score":2075},"",[2067,2070],{"name":2068,"color":2069},"bug","d73a4a",{"name":2053,"color":2054},2338,"[Tabs] Height shifts of 1px between `pill` and `link` variants","2024-10-28T09:49:02Z","https://github.com/nuxt/ui/issues/2338",0.73984593,{"description":2077,"labels":2078,"number":2084,"owner":1988,"repository":2002,"state":2003,"title":2085,"updated_at":2086,"url":2087,"score":2088},"It would be preferable that the module use the protocol that is specified in either the vitest config or nuxt config.\r\n\r\nhttps://github.com/danielroe/nuxt-vitest/blob/178c11865380b0cadb4c4af196486ebba308d3a9/packages/nuxt-vitest/src/module.ts#L49\r\n\r\nThis is resulting in the dev tools being unable to show the proper page for the ui:\r\n\r\n\r\n",[2079,2080,2083],{"name":2068,"color":2069},{"name":2081,"color":2082},"good first issue","7057ff",{"name":1999,"color":2000},548,"devtools iframe not able to run in https","2023-12-05T15:29:38Z","https://github.com/nuxt/test-utils/issues/548",0.74292296,{"description":2090,"labels":2091,"number":2094,"owner":1988,"repository":2059,"state":2003,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Description\n\nI can see there was some changes [here](https://github.com/nuxt/ui/pull/3123) which is great.\n\nI'm just wondering why the 'help' property was excluded from these additions?\n\nThank you!",[2092,2093],{"name":2050,"color":2051},{"name":2053,"color":2054},3685,"Was UFormField 'help' property excluded from the aria-describedby update for any specific reason?","2025-03-26T12:47:39Z","https://github.com/nuxt/ui/issues/3685",0.7566379,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"TCjAh03G3ghpUxIPYRD_Sug2ZbkY4JZoodbxM-iQlng":-1},"/nuxt/nuxt.com/511"]