\n\nI am not sure what happened and when. Just discovered today after cleaning node_modules and reinstalling all packages that tailwind is not loaded correctly. \n\nAs you can see the same is for fresh install from provided starter.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3074,3077,3078],{"name":3075,"color":3076},"bug","d73a4a",{"name":3024,"color":3025},{"name":3079,"color":3080},"upstream","78bddb",3374,"Tailwind CSS 4.0.8 not loading correctly","2025-03-14T20:19:15Z","https://github.com/nuxt/ui/issues/3374",0.7914358,{"description":3087,"labels":3088,"number":3091,"owner":3030,"repository":3031,"state":3055,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Description\n\nI would like to propose the addition of Khmer language support (ភាសាខ្មែរ), which is the national language of Cambodia 🇰🇭. Adding Khmer will enhance accessibility for Khmer-speaking users and improve their experience when using the Nuxt/UI framework.\n\u003Ch1>Motivation\u003C/h1>\nCurrently, the absence of Khmer language support limits usability for a significant number of users who prefer to interact with applications in their native language. By including Khmer, we can:\n1. Broaden our user base in Cambodia and among Khmer-speaking communities worldwide.\n2. Improve user experience and engagement for Khmer-speaking developers and end-users.\n3. Align with our goal of inclusivity and accessibility in software development.\n\u003Ch1>Proposed Implementation\u003C/h1>\n1. Language Files: Create and include translation files for Khmer.\n2. Testing: Ensure that all components are correctly translated and function as expected in Khmer.\n3. Documentation: Update the documentation to reflect the new language support, including usage examples.\n\u003Ch1>Additional Notes\u003C/h1>\nThis is my first time to open a PR in Nuxt UI repo so if there are any specific guidelines or requirements for adding new languages, please let me know, and I would be happy to follow them.\nThank you for considering this request!\n\n### Additional context\n\n_No response_",[3089,3090],{"name":3021,"color":3022},{"name":3024,"color":3025},3118,"Request to Add Khmer Language Support","2025-01-25T13:14:14Z","https://github.com/nuxt/ui/issues/3118",0.79330707,{"description":3097,"labels":3098,"number":3101,"owner":3030,"repository":3031,"state":3055,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.12.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@10.4.1\n- Builder: -\n- User Config: extends, modules, $production, devtools, app, css, site, runtimeConfig, sourcemap, future, experimental, compatibilityDate, nitro, eslint, linkChecker, sitemap\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.13, @nuxtjs/seo@2.1.1, @nuxt/content@3.1.1, @sentry/nuxt/module@8.55.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nNo reproduction is needed. Prop.state is mutated.\n\n### Description\n\nThe current implementation of the Form component has two significant issues:\n\n\n1. **Direct Prop Mutation**: The component directly mutates its `state` prop, which violates Vue's fundamental rules about prop mutation. From Vue's documentation: [https://vuejs.org/guide/components/props.html#one-way-data-flow](https://vuejs.org/guide/components/props.html#one-way-data-flow)\n> \"All props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This prevents child components from accidentally mutating the parent's state, which can make your app's data flow harder to understand.\"\n\n2. **Breaks Immutable State Patterns**: The direct mutation approach is incompatible with modern state management patterns that rely on immutable state updates.\n\nThe problematic code is in the `_validate` function:\n```typescript\nif (opts.transform) {\n Object.assign(props.state, transformedState.value)\n}\n\n```\n\nhttps://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue\n\nLine 182",[3099,3100],{"name":3075,"color":3076},{"name":3024,"color":3025},3354,"Form component violates Vue prop mutation rules and breaks immutable state patterns","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3354",0.7961172,{"description":3107,"labels":3108,"number":3111,"owner":3030,"repository":3031,"state":3055,"title":3112,"updated_at":3103,"url":3113,"score":3114},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3109,3110],{"name":3075,"color":3076},{"name":3024,"color":3025},3220,"Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","https://github.com/nuxt/ui/issues/3220",0.7981147,{"description":3116,"labels":3117,"number":3118,"owner":3030,"repository":3119,"state":3055,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Environment\n\nOS: Windows 10\r\nBrowser: Brave\n\n### Reproduction\n\n1. In nuxt docs, open the [app.config.ts](https://nuxt.com/docs/guide/directory-structure/app-config#app-config-file) or [useRouter](https://nuxt.com/docs/api/composables/use-router) link\r\n2. Look at the Sidebar of the page, multiple routes are styled as active links\n\n### Describe the bug\n\nIn the documentation, the multiple routes having similar names are styled as an active link at the same time\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1228,"nuxt.com","docs: multiple links are styled as active links","2023-10-10T14:45:12Z","https://github.com/nuxt/nuxt.com/issues/1228",0.80564123,{"description":3125,"labels":3126,"number":3127,"owner":3030,"repository":3119,"state":3055,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Environment\n\nNot necessary\n\n### Reproduction\n\nhttps://nuxt.com/\n\n### Describe the bug\n\n1. Go to https://nuxt.com/\r\n2. Check the alt tags for images in cards after `A solution to cover all your needs`. Possibly many others too.\r\n3. See that the value is `[object Object] image`.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://user-images.githubusercontent.com/640208/203802739-c306c698-53dc-47d6-878c-324ec09dc08f.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1231,"docs: alt tag of images is faulty","2023-04-12T10:10:59Z","https://github.com/nuxt/nuxt.com/issues/1231",0.809368,["Reactive",3133],{},["Set"],["ShallowReactive",3136],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBRvw4mEiogZ1nwcYLQH2-q2Ry8WzrGMyvWXtB9DnrFA":-1},"/nuxt/ui/3671"]