\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\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},"triage","ffffff",3583,"nuxt","ui","open","Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.6617784,{"description":1999,"labels":2000,"number":2004,"owner":1991,"repository":1991,"state":1993,"title":2005,"updated_at":2006,"url":2007,"score":2008},"### Environment\nv20.16.0\n\n\n\n\n### Reproduction\n\n---\n\n### Describe the bug\n\n\nWhen start app after build \n\n`The requested module 'node:fs/promises' does not provide an export named 'exists'`\n`The requested module 'fs/promises' does not provide an export named 'exists'`\n\nIn dev mode all work.\n\nWhat is this?\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2001],{"name":2002,"color":2003},"pending triage","E99695",29973,"The requested module 'node:fs/promises' does not provide an export named 'exists'","2024-11-19T15:16:12Z","https://github.com/nuxt/nuxt/issues/29973",0.6811004,{"description":2010,"labels":2011,"number":2016,"owner":1991,"repository":1992,"state":1993,"title":2017,"updated_at":2018,"url":2019,"score":2020},"### Description\r\n\r\n**Problem**\r\nThe current implementation of the keyboard shortcuts composable (defineShortcuts) doesn't work correctly with non-Latin keyboard layouts, such as Arabic. This limits the usability of the composable for users with different language settings.\r\n\r\n**Proposed Solution**\r\nImplement an optional configuration flag '_layoutIndependent_' that, when set to true, makes the composable use KeyboardEvent.code instead of KeyboardEvent.key. This change will allow the shortcuts to work regardless of the keyboard layout or language setting.\r\n\r\n### Additional context\r\n\r\n_No response_",[2012,2015],{"name":2013,"color":2014},"enhancement","a2eeef",{"name":1988,"color":1989},2293,"Add support for non-Latin keyboard layouts in defineShortcuts composable","2025-01-10T07:47:55Z","https://github.com/nuxt/ui/issues/2293",0.6930936,{"description":2022,"labels":2023,"number":2031,"owner":1991,"repository":1991,"state":1993,"title":2032,"updated_at":2033,"url":2034,"score":2035},"### Environment\r\n\r\n浏览器\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/sandbox/pedantic-jones-djcypc?file=%2Fpages%2Findex.vue%3A101%2C10\r\n\r\n### Describe the bug\r\n\r\nError using the 'naive-ui' type\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2024,2025,2028],{"name":2002,"color":2003},{"name":2026,"color":2027},"vite","3574D1",{"name":2029,"color":2030},"upstream","E8A36D",24303,"The requested module '/_nuxt/node_modules/.cache/vite/client/deps/naive-ui.js?v=a31a58c4' does not provide an export named 'FormInst'","2024-06-30T11:06:54Z","https://github.com/nuxt/nuxt/issues/24303",0.6974648,{"description":2037,"labels":2038,"number":2045,"owner":1991,"repository":1992,"state":2046,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nIn my Nuxt 3 project (that uses Nuxt UI `v3.0.0-alpha9`), I have a Vue component like this:\n\n```vue\n\u003Cscript setup lang=\"ts\">\n...\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUContainer class=\"section\">\n ...\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cstyle scoped lang=\"scss\">\n@use \"tailwindcss\";\n\n.section + .section {\n @apply mt-8 lg:mt-12;\n}\n\u003C/style>\n```\n\nThe problem is that `@apply mt-8 lg:mt-12;` doesn't work unless I add this to my `nuxt.config.ts`:\n```\npostcss: {\n plugins: {\n \"@tailwindcss/postcss\": {}, // https://tailwindcss.com/docs/v4-beta#using-post-css\n },\n},\n```\n\nHowever, when I do this, the Nuxt UI components stop working properly (e.g., Slideover renders at the bottom of the page and with wrong styling). How can I make the `@apply ...` work without breaking the Nuxt UI components?\n\nThis is my `package.json`:\n```json\n{\n \"name\": \"frontend\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"postinstall\": \"husky install && nuxt prepare\",\n \"dev\": \"nuxt dev\",\n \"build\": \"nuxt build\",\n \"preview\": \"nuxt preview\"\n },\n \"dependencies\": {\n \"@nuxt/ui\": \"^3.0.0-alpha.9\",\n \"nuxt\": \"latest\",\n \"nuxt-svgo\": \"latest\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"devDependencies\": {\n \"@commitlint/cli\": \"latest\",\n \"@commitlint/config-conventional\": \"latest\",\n \"husky\": \"latest\",\n \"sass\": \"latest\"\n }\n}\n```\n\nThis is my `nuxt.config.ts`:\n```ts\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: \"2024-04-03\",\n devtools: { enabled: false },\n modules: [\"@nuxt/ui\", \"nuxt-svgo\"],\n css: [\"@/assets/css/main.css\"],\n // postcss: {\n // plugins: {\n // \"@tailwindcss/postcss\": {}, // https://tailwindcss.com/docs/v4-beta#using-post-css\n // },\n // },\n appConfig: {\n // https://ui3.nuxt.dev/getting-started/theme#colors\n ui: {\n colors: {\n primary: \"primary\", // Defined in `assets/css/theme.css`\n secondary: \"secondary\", // Defined in `assets/css/theme.css`\n },\n },\n },\n});\n```\n\nThis is my `assets/main.css`:\n```css\n/* https://ui3.nuxt.dev/getting-started/installation/nuxt#import-tailwind-css-and-nuxt-ui-in-your-css */\n@import \"tailwindcss\";\n@import \"@nuxt/ui\";\n```",[2039,2042],{"name":2040,"color":2041},"question","d876e3",{"name":2043,"color":2044},"v3","49DCB8",2772,"closed","@apply Tailwind CSS class in a component's `\u003Cstyle>` tag","2024-12-09T11:14:28Z","https://github.com/nuxt/ui/issues/2772",0.6439355,{"description":2052,"labels":2053,"number":2056,"owner":1991,"repository":1992,"state":2046,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### Environment\n\n\n\nI get this error anytime I try and use \u003CUInput /> even without any other code.\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n`\u003Ctemplate>\n \u003CUContainer>\n \u003CUForm :schema=\"schema\" :state=\"state\" class=\"space-y-4\" @submit=\"onSubmit\">\n \u003CUFormField label=\"Code\" name=\"Code\"\n >\u003CUInput v-model=\"state.code\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { z } from 'zod';\nimport type { FormSubmitEvent } from '#ui/types';\n\nconst supabase = useSupabaseClient();\nconst toast = useToast();\n\n//Form\nconst schema = z.object({\n code: z.string().min(3),\n});\n\ntype Schema = z.output\u003Ctypeof schema>;\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n code: undefined,\n});\n\nasync function onSubmit(event: FormSubmitEvent\u003CSchema>) {\n toast.add({\n title: 'Success',\n description: 'The form has been submitted.',\n color: 'success',\n });\n console.log(event.data);\n}\n\u003C/script>\n`\n\n### Description\n\nUInput causes an error\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2054,2055],{"name":1985,"color":1986},{"name":2043,"color":2044},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.6495345,{"description":2062,"labels":2063,"number":2070,"owner":1991,"repository":2071,"state":2046,"title":2072,"updated_at":2073,"url":2074,"score":2075},"With the pinia nuxt module you can set `autoImports` in the configuration. I have something like this in mine:\r\n\r\n```\r\npinia: {\r\n autoImports: [['defineStore', 'definePiniaStore']],\r\n},\r\n```\r\nThat allows me to auto import `definePiniaStore` which is a reference to `defineStore`. \r\n\r\nThe import is not found when I try to test the store using nuxt-vitest. Is there something nuxt-vitest could do to support them? Or is it something that pinia needs to fix with their module on their end?",[2064,2067],{"name":2065,"color":2066},"vitest-environment","b60205",{"name":2068,"color":2069},"needs reproduction","DE7793",592,"test-utils","Support pinia autoImports","2023-12-02T00:22:10Z","https://github.com/nuxt/test-utils/issues/592",0.6605382,{"description":2077,"labels":2078,"number":2081,"owner":1991,"repository":1992,"state":2046,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2079,2080],{"name":1985,"color":1986},{"name":2043,"color":2044},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.6696159,{"description":2087,"labels":2088,"number":2094,"owner":1991,"repository":1992,"state":2046,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.5.0\n- Nuxt Version: -\n- CLI Version: 3.23.0\n- Nitro Version: -\n- Package Manager: pnpm@10.6.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button#label\n\n### Description\n\nthe buttons should have cursor pointer by default.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2089,2090,2093],{"name":1985,"color":1986},{"name":2091,"color":2092},"duplicate","cfd3d7",{"name":2043,"color":2044},3552,"Button | should have `cursor-pointer` by default","2025-03-19T20:46:13Z","https://github.com/nuxt/ui/issues/3552",0.6761938,{"description":2100,"labels":2101,"number":2103,"owner":1991,"repository":1992,"state":2046,"title":2104,"updated_at":2105,"url":2106,"score":2107},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.5\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: devtools, modules\n- Runtime Modules: @nuxt/ui@2.21.0\n- Build Modules: -\n------------------------------\n\n### Version\n\nv2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/github/nuxt/starter/tree/ui?file=package.json\n\n### Description\n\n`npm run build` on the latest nuxt v3.16 on UI v2.21.0 throws the following error:\n\n`[17:41:35] ERROR .nuxt/dist/server/node_modules/_nuxt/ui/dist/runtime/components/elements/Link.vue.mjs (2:18): \"diff\" is not exported by \"node_modules/ohash/dist/index.mjs\", imported by \".nuxt/dist/server/node_modules/_nuxt/ui/dist/runtime/components/elements/Link.vue.mjs\".`",[2102],{"name":1985,"color":1986},3486,"Generating a production build with nuxt `3.16` throws `ohash` error","2025-03-12T09:19:23Z","https://github.com/nuxt/ui/issues/3486",0.6809549,["Reactive",2109],{},["Set"],["ShallowReactive",2112],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"fxp9qu7_wXR8fQBZO26SwjY8xFrZ1Oo4hb8WxUBwUfs":-1},"/nuxt/icon/367"]