\n\u003C/UTooltip>\n```\n\nThe reason is that both the tooltip and the switch are dependent on the `data-state` property of the element. Switch creates two divs around the button (which `data-state` it follows) but the tooltip targets the same button thus causing problems. The fix would be that the tooltip would use the `data-state` of the outermost switch container div.\n\nWorkaround is to put the switch inside a div like this:\n```\n\u003CUTooltip text=\"tooltip text\">\n \u003Cdiv>\n \u003CUSwitch label=\"switch label\" />\n \u003C/div>\n\u003C/UTooltip>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",3599,"nuxt","ui","open","Switch inside a Tooltip loses styling","2025-03-18T11:56:03Z","https://github.com/nuxt/ui/issues/3599",0.78473586,{"description":1999,"labels":2000,"number":2010,"owner":1991,"repository":1991,"state":1993,"title":2011,"updated_at":2012,"url":2013,"score":2014},"### Environment\n\n```\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.15.0`\r\n- Nuxt Version: `3.0.0-rc.3`\r\n- Package Manager: `npm@8.3.0`\r\n- Builder: `vite`\r\n- User Config: `typescript`, `app`, `css`, `build`, `nitro`, `runtimeConfig`, `vite`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\n\n### Reproduction\n\n-\n\n### Describe the bug\n\nI apologize for using a translator because of my poor English.\r\n\r\nI checked that the class name was changed during the esbuild transform process during the nitro compiling.\r\nSome libraries use class names. In my case, it was the `sequelize-typescript` library.\r\n\r\nA similar issue was mentioned in the esbuild repository. https://github.com/evanw/esbuild/issues/931\r\n\r\nAnd I checked if the `keepNames` option is available in the `nuxt.config` file, but I couldn't find it.\r\n\r\nCan I add an option within the `esbuild` function for the rollup plugin in the `node_modules/nitropack/dist/chunks/prerender.mjs` file?\r\n\r\n```\r\n // node_modules/nitropack/dist/chunks/prerender.mjs:732\r\n return {\r\n name: \"esbuild\",\r\n async transform(code, id) {\r\n ...\r\n const result = await transform(code, {\r\n loader,\r\n target: options.target,\r\n define: options.define,\r\n sourcemap: options.sourceMap,\r\n sourcefile: id,\r\n keepNames: true // *Here\r\n });\r\n ...\r\n },\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2001,2004,2007],{"name":2002,"color":2003},"enhancement","8DEF37",{"name":2005,"color":2006},"nitro","bfd4f2",{"name":2008,"color":2009},"upstream","E8A36D",14134,"Should support keepNames option for esbuild.","2024-06-30T11:10:33Z","https://github.com/nuxt/nuxt/issues/14134",0.7864383,{"description":2016,"labels":2017,"number":2023,"owner":1991,"repository":2024,"state":2025,"title":2026,"updated_at":2027,"url":2028,"score":2029},"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) ?",[2018,2020],{"name":2002,"color":2019},"1ad6ff",{"name":2021,"color":2022},"marketing","f5c828",1048,"nuxt.com","closed","[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.76630956,{"labels":2031,"number":2039,"owner":1991,"repository":1991,"state":2025,"title":2040,"updated_at":2041,"url":2042,"score":2043},[2032,2033,2036],{"name":2002,"color":2003},{"name":2034,"color":2035},"discussion","538de2",{"name":2037,"color":2038},"3.x","29bc7f",12834,"Allow optional build-time type checking","2023-01-19T16:36:14Z","https://github.com/nuxt/nuxt/issues/12834",0.7684585,{"description":2045,"labels":2046,"number":2051,"owner":1991,"repository":1992,"state":2025,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nAccording to the documentation for using slots, we should use the following:\n\n```\n\u003Ctemplate #name-cell=\"{ row }\">\n \u003Cdiv class=\"flex items-center gap-3\">\n {{ row.original.position }}\n \u003C/div>\n\u003C/template>\n\n```\nThe `row.original` object provides access to the row data. However, in previous versions, we could also access the table index like this:\n\n`#name-cell=\"{ row, index }\"\n`\n\nThis allowed us to display a numeric sequence for the table data. With the latest version, is there a way to access an index within the table?\n",[2047,2050],{"name":2048,"color":2049},"question","d876e3",{"name":1988,"color":1989},2729,"How Can I Get the Index When Using Slots in a Table?","2024-11-22T18:49:16Z","https://github.com/nuxt/ui/issues/2729",0.7720189,{"description":2057,"labels":2058,"number":2065,"owner":1991,"repository":1991,"state":2025,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Describe the feature\n\nWe noticed that if a non-existing route middleware is assigned via `definePageMeta()`, there is no build-time validation:\r\n- build passes\r\n- type-check passes\r\n\r\nBut of course during runtime there is an error. We renamed a lot of middlewares in a big project and had to notice the hard way that we forgot some.\r\n\r\nStackBlitz demo: https://stackblitz.com/edit/github-fyckni?file=pages%2Findex.vue\r\n\r\n- `npm run build`\r\n- `npm run type-check`\r\n\r\n**Feature request:** It would be helpful if the type-check and/or build would fail in this case.\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2059,2062],{"name":2060,"color":2061},"types","2875C3",{"name":2063,"color":2064},"🍰 p2-nice-to-have","0E8A16",27860,"Type-check route middleware assignments","2024-08-26T19:57:59Z","https://github.com/nuxt/nuxt/issues/27860",0.7750429,{"labels":2071,"number":2075,"owner":1991,"repository":1991,"state":2025,"title":2076,"updated_at":2077,"url":2078,"score":2079},[2072,2073,2074],{"name":2002,"color":2003},{"name":2037,"color":2038},{"name":2005,"color":2006},14003,"[Kit] Support the method suffix in `addServerHandler`","2023-02-24T22:50:31Z","https://github.com/nuxt/nuxt/issues/14003",0.7809989,{"labels":2081,"number":2085,"owner":1991,"repository":1991,"state":2025,"title":2086,"updated_at":2087,"url":2088,"score":2089},[2082],{"name":2083,"color":2084},"2.x","d4c5f9",7174,"Add pre-commit hook with Husky","2023-01-18T15:36:23Z","https://github.com/nuxt/nuxt/issues/7174",0.7811684,{"description":2091,"labels":2092,"number":2096,"owner":1991,"repository":1991,"state":2025,"title":2097,"updated_at":2098,"url":2099,"score":2100},"It would be great if you could extend *.graphql file detection for the webpack configuration like described here: http://dev.apollodata.com/react/webpack.html\r\n\r\nThis would need to get included:\r\n```\r\nloaders: [\r\n {\r\n test: /\\.(graphql|gql)$/,\r\n exclude: /node_modules/,\r\n loader: 'graphql-tag/loader'\r\n }\r\n]\r\n```\r\n\r\nThanks!\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c131\">#c131\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2093,2095],{"name":2048,"color":2094},"cc317c",{"name":2083,"color":2084},155,"add graphql file detection to webpack config","2023-01-18T15:38:31Z","https://github.com/nuxt/nuxt/issues/155",0.7812851,{"description":2102,"labels":2103,"number":2107,"owner":1991,"repository":1992,"state":2025,"title":2108,"updated_at":2109,"url":2110,"score":2111},"### Description\n\nCurrently, `UPageCTA` does not provide a way to customize its primary color when using the solid variant. It would be useful to have a color prop similar to other components, allowing developers to define the primary color (primary, secondary, etc.).\n\n\n\n### Additional context\n\n_No response_",[2104,2106],{"name":2002,"color":2105},"a2eeef",{"name":1988,"color":1989},3309,"Add color prop to `UPageCTA`","2025-03-08T12:21:56Z","https://github.com/nuxt/ui/issues/3309",0.78367513,["Reactive",2113],{},["Set"],["ShallowReactive",2116],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"6FnBp3MujzSO1PBOvhubHThLECqYWq6CgK8QAvV6C-I":-1},"/nuxt/nuxt.com/435"]