\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```",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"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.64588696,{"description":2882,"labels":2883,"number":2887,"owner":2874,"repository":2874,"state":2876,"title":2888,"updated_at":2889,"url":2890,"score":2891},"### 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```",[2884],{"name":2885,"color":2886},"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.6855629,{"description":2893,"labels":2894,"number":2899,"owner":2874,"repository":2875,"state":2876,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### 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_",[2895,2898],{"name":2896,"color":2897},"enhancement","a2eeef",{"name":2871,"color":2872},2293,"Add support for non-Latin keyboard layouts in defineShortcuts composable","2025-01-10T07:47:55Z","https://github.com/nuxt/ui/issues/2293",0.69160914,{"description":2905,"labels":2906,"number":2913,"owner":2874,"repository":2875,"state":2914,"title":2915,"updated_at":2916,"url":2917,"score":2918},"### 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```",[2907,2910],{"name":2908,"color":2909},"question","d876e3",{"name":2911,"color":2912},"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.63561267,{"description":2920,"labels":2921,"number":2924,"owner":2874,"repository":2875,"state":2914,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### 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_",[2922,2923],{"name":2868,"color":2869},{"name":2911,"color":2912},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.6494764,{"description":2930,"labels":2931,"number":2934,"owner":2874,"repository":2875,"state":2914,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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```",[2932,2933],{"name":2868,"color":2869},{"name":2911,"color":2912},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.66024995,{"description":2940,"labels":2941,"number":2948,"owner":2874,"repository":2949,"state":2914,"title":2950,"updated_at":2951,"url":2952,"score":2953},"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?",[2942,2945],{"name":2943,"color":2944},"vitest-environment","b60205",{"name":2946,"color":2947},"needs reproduction","DE7793",592,"test-utils","Support pinia autoImports","2023-12-02T00:22:10Z","https://github.com/nuxt/test-utils/issues/592",0.6712226,{"description":2955,"labels":2956,"number":2962,"owner":2874,"repository":2875,"state":2914,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### 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```",[2957,2958,2961],{"name":2868,"color":2869},{"name":2959,"color":2960},"duplicate","cfd3d7",{"name":2911,"color":2912},3552,"Button | should have `cursor-pointer` by default","2025-03-19T20:46:13Z","https://github.com/nuxt/ui/issues/3552",0.67644405,{"description":2968,"labels":2969,"number":2972,"owner":2874,"repository":2973,"state":2914,"title":2974,"updated_at":2975,"url":2976,"score":2977},"Hover color should be green on `ProseA`\n\n\n\nReading [typography tokens](https://github.com/nuxt-themes/typography/blob/main/tokens.config.ts), colors should be declared inside `tokens.config.ts` this way.\n\n(Tried with `colors` and `color`, both don't work)\n\n```js\nexport default defineTheme({\n typography: {\n color: {\n // palette() returns the good color scheme\n primary: palette('#00dc82')\n }\n }\n})\n```",[2970],{"name":2868,"color":2971},"ff281a",1076,"nuxt.com","[Typography] ProseA hover color not applied","2023-06-06T12:14:34Z","https://github.com/nuxt/nuxt.com/issues/1076",0.6860463,{"description":2979,"labels":2980,"number":2982,"owner":2874,"repository":2875,"state":2914,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### 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\".`",[2981],{"name":2868,"color":2869},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.68609774,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ffxp9qu7_wXR8fQBZO26SwjY8xFrZ1Oo4hb8WxUBwUfs":-1},"/nuxt/icon/367"]