\n\n\n### Description\n\nIn Nuxt UI v3, the \u003CUTable /> component does not provide any trigger event when clicking on a table row. In contrast, the v2 version included the @select event, which allowed developers to handle row clicks effectively. This regression impacts the ability to implement common interaction patterns, such as handling row selection or performing actions based on user clicks.\n\nDoes Nuxt UI v3 have an event similar to the @select event from v2 for the \u003CUTable /> component? Specifically, is there a way to trigger an event when a table row is clicked?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2029,2032],{"name":2030,"color":2031},"bug","d73a4a",{"name":2019,"color":2020},3010,"UTable row click event UI3","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3010",0.79944724,{"description":2039,"labels":2040,"number":2056,"owner":1988,"repository":1988,"state":1990,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v18.7.0`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `srcDir`, `modules`, `compilerOptions`, `vue`, `vite`, `telemetry`, `algolia`, `head`, `auth`, `css`, `build`, `runtimeConfig`\r\n- Runtime Modules: `genesis-design-system/nuxt`, `@nuxtjs/tailwindcss@5.3.5`, `@nuxtjs/algolia@1.1.4`, `@nuxtjs-alt/auth@2.0.20`, `@nuxtjs/device@3.0.0`, `unplugin-icons/nuxt`, `@pinia/nuxt@0.4.3`, `@nuxtjs/i18n@8.0.0-alpha.3`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nwe are crawling our website with screaming frog...\r\n\r\nWhen we have about 1,500 urls tracked, the server crashes and starts throwing 503 errors.\r\n\r\n\r\n\r\nAnd at that moment we try to make a request through the browser and it is already impossible.\r\n\r\nYou have to stop the server and start it again\r\n\r\n\r\n\r\n\n\n### Describe the bug\n\nwe are crawling our website with screaming frog...\r\n\r\nWhen we have about 1,500 urls tracked, the server crashes and starts throwing 503 errors.\r\n\r\n\r\n\r\nAnd at that moment we try to make a request through the browser and it is already impossible.\r\n\r\nYou have to stop the server and start it again\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\nError: socket hang up\r\n at connResetException (node:internal/errors:704:14)\r\n at Socket.socketOnEnd (node:_http_client:505:23)\r\n at Socket.emit (node:events:525:35)\r\n at Socket.emit (node:domain:489:12)\r\n at endReadableNT (node:internal/streams/readable:1359:12)\r\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)\n```\n",[2041,2044,2047,2050,2053],{"name":2042,"color":2043},"3.x","29bc7f",{"name":2045,"color":2046},"pending triage","E99695",{"name":2048,"color":2049},"nitro","bfd4f2",{"name":2051,"color":2052},"needs reproduction","FBCA04",{"name":2054,"color":2055},"⛔️ can be closed","484893",15188,"503 Server Unavailable","2023-12-18T15:26:38Z","https://github.com/nuxt/nuxt/issues/15188",0.8037191,{"description":2062,"labels":2063,"number":2066,"owner":1988,"repository":1989,"state":1990,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n Operating System: Linux\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@9.1.1, @nuxt/ui@3.0.0-alpha.10, @pinia/nuxt@0.9.0, nuxt-viewport@2.2.0, @nuxthub/core@0.8.7, nuxt-auth-utils@0.5.6, @nuxt/fonts@0.10.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n```vue\n//dont work\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\" multiple\n @update:model-value=\"testFunctionArray\" @change=\"testFunctionArray\"\n v-model=\"row.original.permissionsModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n```vue\n//work fine\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\"\n @update:model-value=\"testFunction\" @change=\"testFunction\"\n v-model=\"row.original.permissionModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n### Description\n\n`testFunctionArray` is never called if multiple prop is set to true\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2064,2065],{"name":2030,"color":2031},{"name":2019,"color":2020},2953,"USelect with multiple prop does not trigger event when model-value change","2025-01-25T13:12:19Z","https://github.com/nuxt/ui/issues/2953",0.8037353,{"description":2072,"labels":2073,"number":2075,"owner":1988,"repository":1989,"state":1990,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v22.3.0`\r\n- Nuxt Version: `3.13.1`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `yarn@1.22.22`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`, `modules`, `plugins`, `runtimeConfig`, `i18n`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxtjs/i18n@8.5.1`\r\n- Build Modules: `-`\r\n\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts\n\n### Description\n\n## Description\r\nThe Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:\r\n\r\nThe notification component occupies part of the screen unnecessarily.\r\nIt overlaps other elements on the page due to its z-index, potentially disrupting the user interface.\r\n\r\n## Expected Behavior\r\nThe notification component should only be created and added to the DOM when a toast is actually triggered.\r\n\r\n## Current Behavior\r\nThe notification component is always present in the DOM, regardless of whether a toast has been triggered or not.\r\n\r\n## Steps to Reproduce\r\n\r\n- Implement the Nuxt UI notification component in a project.\r\n- Inspect the DOM without triggering any toasts.\r\n- Observe that the notification component is present and has a z-index applied.\r\n\r\n## Additional Context\r\nThis issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.\r\n\r\n## Possible Solution\r\nConsider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).\r\n\u003Cimg width=\"1427\" alt=\"Screenshot 2024-09-04 at 6 29 00 PM\" src=\"https://github.com/user-attachments/assets/da90352f-71e6-4aaf-9bda-7a9e4a3fd056\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2074],{"name":2030,"color":2031},2113,"Notification component created even when toast is not triggered, causing z-index issues","2024-11-09T10:24:37Z","https://github.com/nuxt/ui/issues/2113",0.8051459,{"description":2081,"labels":2082,"number":2087,"owner":1988,"repository":1988,"state":1990,"title":2088,"updated_at":2089,"url":2090,"score":2091},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT` (Windows 10 latest update)\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `telemetry`, `modules`, `css`, `hooks`, `vite`\r\n- Runtime Modules: `nuxt-icon@0.1.8`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n```\r\nexport default defineNuxtConfig({\r\n telemetry: false,\r\n modules: [\r\n 'nuxt-icon'\r\n ],\r\n css: [\r\n 'bulma',\r\n ],\r\n hooks: {\r\n 'builder:watch': console.log\r\n },\r\n vite: {\r\n server: {\r\n watch: {\r\n usePolling: true\r\n }\r\n }\r\n }\r\n})\r\n```\r\n```\r\n{\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\"\r\n },\r\n \"devDependencies\": {\r\n \"nuxt\": \"3.0.0\",\r\n \"nuxt-icon\": \"^0.1.8\",\r\n \"sass\": \"^1.57.0\",\r\n \"sass-loader\": \"10\"\r\n },\r\n \"dependencies\": {\r\n \"bulma\": \"^0.9.4\"\r\n }\r\n}\r\n```\r\n\r\n\r\n### Reproduction\r\n\r\n1. Have this in `app.vue` : `\u003Ctemplate>\u003CNuxtPage />\u003C/template>` do not make a \"pages\" directory yet\r\n3. Start server using `yarn dev -o`\r\n4. Add pages/hello.vue with `\u003Ctemplate>Hello world!\u003C/template>` -- this will work\r\n5. Now add pages/test.vue with `\u003Ctemplate>Test\u003C/template>` -- this will 404\r\n\r\nDemo:\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nNew pages require server start, otherwise you get a 404. It breaks the whole point of HMR and productivity. Such a critical issue has been raised (and closed) at least 5 times, over a year without lasting fix. \r\n\r\nhttps://github.com/nuxt/nuxt.js/issues/13307 (raised Jan 26!)\r\nhttps://github.com/nuxt/nuxt.js/issues/13725\r\nhttps://github.com/nuxt/nuxt.js/issues/13791\r\nhttps://github.com/nuxt/nuxt.js/issues/15045\r\nhttps://github.com/nuxt/nuxt.js/issues/15141\r\n\r\nHaving to stop and start the server takes up to 30 seconds (avg. 20s+) for me on an almost empty project. Please fix.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2083,2084,2085],{"name":2042,"color":2043},{"name":2030,"color":2031},{"name":2086,"color":2052},"🔨 p3-minor",15651,"New pages 404 unless server is restarted","2023-01-25T12:25:00Z","https://github.com/nuxt/nuxt/issues/15651",0.8069232,{"description":2093,"labels":2094,"number":2100,"owner":1988,"repository":1989,"state":1990,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### Environment\n\n System:\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\n Memory: 44.48 GB / 62.57 GB\n Container: Yes\n Shell: 5.9 - /usr/bin/zsh\n Browsers:\n Chrome: 126.0.6478.126\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/select-menu\n\n### Description\n\n1. open docs\n2. open any select menu\n3. select any option\n4. tab to next field\n5. tab index is reset\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2095,2096,2097],{"name":2030,"color":2031},{"name":2019,"color":2020},{"name":2098,"color":2099},"reka-ui","56d799",2350,"[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.8097638,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"QdhIEk9MJ8awwXDC7hLA28jmY8XmPsXdtYFyHgvIj68":-1},"/nuxt/ui/1737"]