work in Storybook? Thank you",[1984],{"name":1985,"color":1986},"question","d876e3",77,"nuxt","icon","open","How do we make nuxt-icon work in Storybook?","2025-01-17T10:54:58Z","https://github.com/nuxt/icon/issues/77",0.7319083,{"description":1996,"labels":1997,"number":2004,"owner":1988,"repository":2005,"state":1990,"title":2006,"updated_at":2007,"url":2008,"score":2009},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.15.4\nCLI Version: 3.13.2\nNitro Version: 2.10.4\nPackage Manager: npm@11.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n.\n\n### Description\n\nHi\nWhen we use the arrow in the DropdownMenu component, a border is added to the last item. Apparently, this is because the arrow element is added at the end of the items groups in this component.\n\n\n\n\n\nI hope I was able to tell you what I meant. It's nothing special, but it would be great if it could be fixed. 🙄\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[1998,2001],{"name":1999,"color":2000},"bug","d73a4a",{"name":2002,"color":2003},"v3","49DCB8",3315,"ui","arrow causes appear border in the last item of DropdownMenu","2025-02-17T11:48:29Z","https://github.com/nuxt/ui/issues/3315",0.75748014,{"description":2011,"labels":2012,"number":2014,"owner":1988,"repository":2015,"state":1990,"title":2016,"updated_at":2017,"url":2018,"score":2019},"### 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",[2013],{"name":1999,"color":2000},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.77063495,{"description":2021,"labels":2022,"number":2030,"owner":1988,"repository":2015,"state":1990,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v21.6.1\r\n- Nuxt Version: 3.12.1\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: bun@1.1.21\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, modules\r\n- Runtime Modules: @nuxt/test-utils/module@^3.14.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-test-with-css-modules-sz2wlg?file=%2Fsandbox.config.json%3A4%2C25-4%2C37\n\n### Describe the bug\n\nWhen running tests on components that uses CSS Modules, the $style attribute is consistently set to undefined, causing the tests to fail.\n\n### Additional context\n\nThere are no examples in the Nuxt test examples folder that include CSS modules. I've read the documentation for @nuxt/test-utils, and it doesn't mention how to use it with CSS modules. I tried googling it, but I couldn't find any information on how to test Vue components with CSS modules. I only found an unanswered question regarding the same issue, e.g., https://github.com/nuxt/test-utils/discussions/804. Since CSS modules work with Nuxt 'out of the box,' I believe testing components that use CSS modules should also work seamlessly.\r\n\n\n### Logs\n\n```shell-script\n❯ test.nuxt.test.ts (1) 5010ms\r\n × my test 5009ms\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n FAIL test.nuxt.test.ts > my test\r\nError: Test timed out in 5000ms.\r\nIf this is a long-running test, pass a timeout value as the last argument or configure it globally with \"testTimeout\".\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\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: Cannot read properties of undefined (reading 'someCssModuleClassName')\r\n ❯ Proxy._sfc_render app.vue:3:20\r\n 1| \u003Ctemplate>\r\n 2| \u003Cdiv :class=\"$style.someCssModuleClassName\">\r\n 3| \u003CNuxtWelcome />\r\n | ^\r\n 4| \u003C/div>\r\n 5| \u003C/template>\r\n ❯ Proxy.clonedComponent.render node_modules/.pnpm/@nuxt+test-utils@3.14.0_@vue+test-utils@2.4.6_h3@1.12.0_happy-dom@14.12.3_nitropack@2.9.7_pla_3tccdhrwarphrx6od5vsqeppdq/node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:142:37\r\n ❯ renderComponentRoot node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6267:16\r\n ❯ ReactiveEffect.componentUpdateFn [as fn] node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4942:46\r\n ❯ ReactiveEffect.run node_modules/.pnpm/@vue+reactivity@3.4.37/node_modules/@vue/reactivity/dist/reactivity.cjs.js:181:19\r\n ❯ instance.update node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5073:16\r\n ❯ setupRenderEffect node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5083:5\r\n ❯ mountComponent node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4851:7\r\n ❯ processComponent node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4805:9\r\n ❯ patch node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4334:11\r\n\r\nThis error originated in \"test.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 \"my test\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- If the error occurred after the test had been completed, this was the last documented test before it was thrown.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n Test Files 1 failed (1)\r\n Tests 1 failed (1)\r\n Errors 1 error\r\n Start at 18:00:20\r\n Duration 5.24s\n```\n",[2023,2024,2027],{"name":1999,"color":2000},{"name":2025,"color":2026},"good first issue","7057ff",{"name":2028,"color":2029},"vitest-environment","b60205",910,"Testing components that use CSS modules is failing","2024-12-19T21:35:48Z","https://github.com/nuxt/test-utils/issues/910",0.77722293,{"description":2036,"labels":2037,"number":2043,"owner":1988,"repository":2005,"state":1990,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### Reproduction\n\n````\n\u003Ctemplate>\n \u003CUChip text=\"test\" size=\"3xl\">\n \u003CUButton icon=\"i-lucide-mail\" color=\"neutral\" variant=\"subtle\" />\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",[2038,2039,2040],{"name":1999,"color":2000},{"name":2002,"color":2003},{"name":2041,"color":2042},"triage","ffffff",3633,"Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.78195226,{"description":2049,"labels":2050,"number":2057,"owner":1988,"repository":2058,"state":2059,"title":2060,"updated_at":2061,"url":2062,"score":2063},"### Welcome Hero\n- [x] Add Illustration to the right (inspiration new docus)\n- [x] Update Logos for devs\n- [x] Update buttons styles and link (video fireship: Nuxt in 120 secondes)\n### Community Section\n- [x] Update button styles",[2051,2054],{"name":2052,"color":2053},"design","00bd6f",{"name":2055,"color":2056},"dev","018415",1341,"nuxt.com","closed","Home Page","2023-07-25T08:52:06Z","https://github.com/nuxt/nuxt.com/issues/1341",0.75831044,{"description":2065,"labels":2066,"number":2072,"owner":1988,"repository":2005,"state":2059,"title":2073,"updated_at":2074,"url":2075,"score":2076},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.12.2`\n- Nuxt Version: `3.14.159`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `bun@1.1.33`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/ui@3.0.0-alpha.8`, `@nuxt/eslint@0.6.1`, `@vueuse/nuxt@11.2.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\nPlace SelectMenu with search in Modal then try to access search input\n\n### Description\n\nSelectMenu search not working from modal\nIt's working if :portal=\"false\", but style broken\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2067,2068,2069],{"name":1999,"color":2000},{"name":2002,"color":2003},{"name":2070,"color":2071},"reka-ui","56d799",2657,"SelectMenu search not clickable from modal","2025-02-13T18:27:29Z","https://github.com/nuxt/ui/issues/2657",0.75896937,{"description":2078,"labels":2079,"number":2080,"owner":1988,"repository":2058,"state":2059,"title":2081,"updated_at":2082,"url":2083,"score":2084},"",[],990,"[Docs] Add pagination","2023-04-04T08:06:43Z","https://github.com/nuxt/nuxt.com/issues/990",0.76744795,{"description":2086,"labels":2087,"number":2014,"owner":1988,"repository":2058,"state":2059,"title":2091,"updated_at":2092,"url":2093,"score":2019},"Blocked by #720 ",[2088],{"name":2089,"color":2090},"enhancement","1ad6ff","[Community] Nuxters filter to select community only","2022-07-25T13:34:54Z","https://github.com/nuxt/nuxt.com/issues/684",{"description":2095,"labels":2096,"number":2098,"owner":1988,"repository":2058,"state":2059,"title":2099,"updated_at":2100,"url":2101,"score":2102},"Blocked by #302 for the data\n\n- [x] Hover to know on what branch/file they are working on.\n- [x] Click on user to switch to his branch and current file",[2097],{"name":2089,"color":2090},330,"Project socket users navigation","2022-04-20T15:43:43Z","https://github.com/nuxt/nuxt.com/issues/330",0.7742859,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"ykzrQI2qiq0u_of-pXnUd8jdYmveihOQE_e2ZB80_PQ":-1},"/nuxt/nuxt.com/1619"]