` rows. `@select` brings you part of the way there, but doesn't make it easy to get access to the full underlying event, for example to check if the user is holding the \u003Ckey>Ctrl\u003C/key>.\n\nSimilarly, even with `@select` I can't see any easy way to focus the table rows using keyboard input. \n\n### Additional context\n\n_No response_",[1984,1987],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"triage","ffffff",2796,"nuxt","ui","open","UTable row click event","2025-01-23T09:56:08Z","https://github.com/nuxt/ui/issues/2796",0.6992692,{"description":1999,"labels":2000,"number":2001,"owner":1991,"repository":2002,"state":1993,"title":2003,"updated_at":2004,"url":2005,"score":2006},"### Environment\n\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.9.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: yarn@4.5.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n\n### Reproduction\n\nI haven't changed the code itself, but uninstalled some dependencies and updated everything to latest.\n\nModules used:\n\n```\n modules: [\n \"@unocss/nuxt\",\n \"@nuxt/content\",\n \"@vueuse/nuxt\",\n \"@nuxt/fonts\",\n // @ts-ignore\n \"@nuxtjs/seo\",\n \"@nuxt/icon\",\n \"nuxt-umami\"\n ],\n```\n\nDependencies upgraded:\n\n\n\n\n\n\nTransitive deps of \"@nuxt/icon\"\n\n\n\nI've tried it with and without the icon config in nuxt.config.ts with no effect\n\n### Describe the bug\n\nI`m suddenly getting this error after upgrading a few dependencies and the site is not loading anymore.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```\nCannot read properties of undefined (reading 'provider')\nStacktrace\nsetup\n@nuxt/icon/dist/runtime/plugin.js:16:17\n(anonymous)\n./C:/Users/MyPC/Workspace/my-project/apps/my-app/virtual:nuxt:C:/Users/MyPC/Workspace/my-project/apps/my-app/.nuxt/plugins/server.mjs:77:89\nModule.executeAsync\nunctx/dist/index.mjs:111:19\nsetup\n./C:/Users/MyPC/Workspace/my-project/apps/my-app/virtual:nuxt:C:/Users/MyPC/Workspace/my-project/apps/my-app/.nuxt/plugins/server.mjs:77:65\n(anonymous)\nnuxt/dist/app/nuxt.js:146:60\nfn\nnuxt/dist/app/nuxt.js:228:44\nObject.callAsync\nunctx/dist/index.mjs:68:55\n(anonymous)\nnuxt/dist/app/nuxt.js:231:56\nObject.runWithContext\n@vue/runtime-core/dist/runtime-core.cjs.js:3940:18\ncallWithNuxt\nnuxt/dist/app/nuxt.js:231:24\n```\n\nBesides these logs from the devtools plugins I see nothing in the actual logs, even with debug and dev flag",[],293,"icon","Cannot read properties of undefined (reading 'provider') - nuxt apps not starting anymore","2024-11-04T12:44:48Z","https://github.com/nuxt/icon/issues/293",0.72941136,{"description":2008,"labels":2009,"number":2014,"owner":1991,"repository":1992,"state":1993,"title":2015,"updated_at":2016,"url":2017,"score":2018},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.8.2\r\n- Builder: -\r\n- User Config: extends, devtools, vite, ignore, hooks, app, css, modules, supabase, dayjs, runtimeConfig, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.2, @nuxt/test-utils/module@3.14.1, nuxt-lodash@2.5.3, @pinia/nuxt@0.5.4, @vueuse/nuxt@11.0.1, @nuxtjs/supabase@1.3.5, @nuxt/ui@2.18.4, dayjs-nuxt@2.1.9\r\n- Build Modules: -\n\n### Version\n\n2.18.4\n\n### Reproduction\n\nn/a\n\n### Description\n\nI was struggling to figure out my TypeScript error and I only found the solution from this issue's stackblitz example: https://github.com/nuxt/ui/issues/1604\r\n\r\nThe example in the docs provided here does not provide a complete TypeScript example, even though the component is written using `lang=\"ts\"`. https://ui.nuxt.com/components/modal#control-programmatically\r\n\r\nThe use of `defineEmits` must be typed in order for the magical event listeners (such as `onSuccess`) to be picked up by the LSP. I recommend fixing the TS example or omitting `lang=\"ts\"` from the example.\r\n\r\nThanks for the great library!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2010,2013],{"name":2011,"color":2012},"bug","d73a4a",{"name":1988,"color":1989},2085,"useModal example docs missing TypeScript defineEmits usage","2024-08-27T14:32:02Z","https://github.com/nuxt/ui/issues/2085",0.73081315,{"description":2020,"labels":2021,"number":2027,"owner":1991,"repository":1992,"state":1993,"title":2028,"updated_at":2029,"url":2030,"score":2031},"### Environment\n\n- Operating System: `Windows 11`\n- Browser: `Chrome 131`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt UI\n\n### Version\n\nv2.20.0, 3.0.0-alpha-x\n\n### Reproduction\n\n[Tabs ](https://ui.nuxt.com/components/tabs) and [Input#disabled](https://ui.nuxt.com/components/input#disabled) sections of ui.nuxt.com, as well as pretty much every other component that has a \"Disabled\" state, demonstrate the issue\n\n### Description\n\nThe current styling for `disabled` state of different components in Nuxt UI has a very subtle visual distinction from the enabled state. On a monitor with good sRGB calibration (Gigabyte M32U - IPS, 4K, sRGB mode), the grayed-out appearance of the `disabled` state in almost every Nuxt UI component (as shown on the [ui.nuxt.com/components](https://ui.nuxt.com/components)) is almost indistinguishable from the non-disabled state.\n\n**Issue:**\n- Disabled elements do not provide a clear visual cue, making it hard for users to differentiate their state at a glance.\n- This affects usability and accessibility, especially for users with mild visual impairments or varying screen settings.\n\n**Suggestion:**\n\nConsider increasing contrast differences or adding clearer indicators (e.g., opacity) to improve visual accessibility for disabled elements.\n\n**Example:**\n[Tabs](https://ui.nuxt.com/components/tabs) and [Input#disabled](https://ui.nuxt.com/components/input#disabled) sections of ui.nuxt.com, as well as pretty much every other component that has a \"Disabled\" state, demonstrate the issue.\n\n**Video** (may look different on your monitor):\nNuxt UI `2.20.0`:\n\n\nhttps://github.com/user-attachments/assets/81eea3ee-1c74-4036-9fe9-55b18cb16851\n\n\nNuxt UI `3.0.0-alpha-x`:\n\n\nhttps://github.com/user-attachments/assets/9018589e-98fb-46d1-97e5-623fae98727e\n\n\n**Photos** of how it looks like on the mentioned monitor:\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/97736e43-fe88-428a-b3b2-67fcbe9b37dc\" width=\"400\"/>\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/6caf4ee6-0cb9-4c7e-9bc7-07e320248b8e\" width=\"400\"/>\n\n\u003Cimg src=\"https://github.com/user-attachments/assets/b64d9960-4877-4fc4-b016-92ce8c4cf393\" width=\"400\"/>\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2022,2023,2026],{"name":2011,"color":2012},{"name":2024,"color":2025},"v3","49DCB8",{"name":1988,"color":1989},2995,"Improve disabled state visibility for Tabs and other components","2024-12-29T13:39:36Z","https://github.com/nuxt/ui/issues/2995",0.74007964,{"description":2033,"labels":2034,"number":2035,"owner":1991,"repository":2002,"state":2036,"title":2037,"updated_at":2038,"url":2039,"score":2040},"With the release of `v1.10` we should be able to use arbitrary icon names by setting `normalizeIconName` option to `false`, however it does not seem to work.\n\nI followed the documentation, but my local collection icons witn non-convential names failing to load.\n\nMy module config:\n```ts\n modules: ['@nuxt/icon'],\n icon: {\n customCollections: [\n {\n prefix: 'my-icon',\n dir: './assets/my-icons',\n normalizeIconName: false, // \u003C-- this\n },\n ],\n },\n```\n\nBut when I'm trying to use `assets/my-icons/FooBar.svg` as `\u003CIcon name=\"my-icon:FooBar\" />`, I'm getting the warning\n```\n[Icon] failed to load icon my-icon:FooBar\n```\n\n`\u003CIcon name=\"my-icon:foo-bar\" />` also fails to load, which is expected as normalize is disabled.\n\nReproduction link: [stackblitz](https://stackblitz.com/edit/github-zgzqz3vo?file=app.vue)\n\nSetup: Nuxt v3.14.1592, nuxt-icon v1.10.1.",[],322,"closed","new custom collection option `normalizeIconName: false` does not work as expected","2024-12-16T07:04:54Z","https://github.com/nuxt/icon/issues/322",0.6787951,{"labels":2042,"number":2049,"owner":1991,"repository":1991,"state":2036,"title":2050,"updated_at":2051,"url":2052,"score":2053},[2043,2046],{"name":2044,"color":2045},"3.x","29bc7f",{"name":2047,"color":2048},"pending triage","E99695",14450,"navigateTo and useRouter path change with different layouts doesn't load dom elements in client side mode (no ssr)","2023-01-26T16:25:09Z","https://github.com/nuxt/nuxt/issues/14450",0.7133199,{"description":2055,"labels":2056,"number":2057,"owner":1991,"repository":2002,"state":2036,"title":2058,"updated_at":2059,"url":2060,"score":2061},"After installing an `@iconify-json/*` package (`@iconify-json/mdi` in my scenario), the following error gets spit out when the `/api/_nuxt_icon/:collection` endpoint is called\r\n\r\n\r\n\r\nIt seems to be caused by the dynamic import missing the json import attribute on line 120 of `module.ts` https://github.com/nuxt/icon/blob/85a0e7b940725561f35656d75a99179f88cecef8/src/module.ts#L120 \r\n\r\nAdding `{ with: { type: 'json' } }` as a second parameter resolves the error for me:\r\n\r\n```js\r\nimport('@iconify-json/${collection}/icons.json', { with: { type: 'json' } }).then(m => m.default)`\r\n```",[],186,"Locally installed `@iconify-json/*` packages result in 'needs an import attribute of type \"json\"' error","2024-07-15T15:35:07Z","https://github.com/nuxt/icon/issues/186",0.7218319,{"description":2063,"labels":2064,"number":2065,"owner":1991,"repository":2002,"state":2036,"title":2066,"updated_at":2067,"url":2068,"score":2069},"Since this commit 36e38c32f8f1f61570080e4e95f51cf249229a1a (I guess), when I open pm2 logs, I get a lot of console.log from nuxt icon\n\n\nIs there a way to disable it?",[],299,"Disable console.log","2024-11-19T01:11:23Z","https://github.com/nuxt/icon/issues/299",0.7268284,{"description":2071,"labels":2072,"number":2078,"owner":1991,"repository":1991,"state":2036,"title":2079,"updated_at":2080,"url":2081,"score":2082},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@3.2.0\r\n- Builder: vite\r\n- User Config: alias, app, components, css, devtools, experimental, extends, i18n, modules, nitro, pinia, router, runtimeConfig, tailwindcss, telemetry, veeValidate, vite, vue\r\n- Runtime Modules: @pinia/nuxt@^0.4.11, @nuxtjs/stylelint-module@^5.1.0, @nuxtjs/i18n@8.0.0-beta.13, @vueuse/nuxt@10.2.1, @vee-validate/nuxt@^4.9.6, @nuxtjs/tailwindcss@^6.8.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\nI provide a minimal reproduction\r\n\r\nhttps://stackblitz.com/edit/github-brcyvh?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nI'm using a plugin `$bp` that use `useBreakpoints` from `vueuse` under the hood https://vueuse.org/core/useBreakpoints\r\n\r\nMy goal is to change the `size` of the component `NButton` based on a boolean : `$bp.isLapM`.\r\n\r\nWhen we refresh the page, we see that the `btnSize` inside the button is updated but the class still `-sm`.\r\nIf I resize my window, both are updated\r\n\r\nWe are migrating our app to Nuxt 3, and on Nuxt 2 we didn't have this issue... :cry: \r\n\r\nI'm a doing something wrong about this ? \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_",[2073,2074,2075],{"name":2044,"color":2045},{"name":2047,"color":2048},{"name":2076,"color":2077},"upstream","E8A36D",22722,"class / style attribute does not update on node mismatch","2023-08-23T10:38:59Z","https://github.com/nuxt/nuxt/issues/22722",0.72722965,{"description":2084,"labels":2085,"number":2094,"owner":1991,"repository":1991,"state":2036,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.10.0`\r\n- Nuxt Version: `3.11.2`\r\n- CLI Version: `3.11.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `npm@10.2.3`\r\n- Builder: `-`\r\n- User Config: `css`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://github.com/DallasHoff/nuxt-fouc-example\n\n### Describe the bug\n\nUnder certain conditions, I am seeing a flash of unstyled content in the production build of a site since Nuxt 3.10.0. In the provided reproduction, you can see this by building the site (`npm run build`) and then previewing it (`npm run preview`) and watching as the page loads. The links in the navbar will start out unstyled, in a vertical stack, and then switch to being styled in a row.\r\n\r\nIf you then downgrade the project to Nuxt 3.9.3 with no other changes, the FOUC will not happen. Checking the built HTML of the page, you can see that this version has the CSS of the navbar component inlined, where newer versions of Nuxt do not.\r\n\r\nStrangely, the FOUC also only happens with certain configurations of the components. The FOUC does not happen if:\r\n- The `\u003Cstyle>` tag in `layouts/default.vue` is empty.\r\n- The `\u003Cscript>` tag in `components/app/navbar.vue` does not have `lang=\"ts\"`\r\n\r\n#25806 is similar, but that was resolved as an issue with Vite while this issue happens in production and not development. The issue appears if either `nuxt build` or `nuxt generate` is used to build the site.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2086,2087,2088,2091],{"name":2044,"color":2045},{"name":2011,"color":2012},{"name":2089,"color":2090},"🔨 p3-minor","FBCA04",{"name":2092,"color":2093},"inline styles","68AF97",27334,"FOUC in Production since Nuxt 3.10.0","2024-12-03T11:32:03Z","https://github.com/nuxt/nuxt/issues/27334",0.73217124,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"gs6XpSaNP-G35qeprCDHbDEHxCYnE58Ah67ECMsUDys":-1},"/nuxt/fonts/106"]