\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2909,2910,2913],{"name":2868,"color":2869},{"name":2911,"color":2912},"needs reproduction","CB47CF",{"name":2871,"color":2872},3546,"closed","`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.6456858,{"description":2921,"labels":2922,"number":2925,"owner":2877,"repository":2926,"state":2915,"title":2927,"updated_at":2928,"url":2929,"score":2930},"https://volta.s3.fr-par.scw.cloud/Screenshot_2022_04_26_at_15_17_43_ca013064d2.mp4\n",[2923],{"name":2868,"color":2924},"ff281a",407,"nuxt.com","`CMD+B` in editor should not open the branch modal","2022-04-26T14:28:31Z","https://github.com/nuxt/nuxt.com/issues/407",0.69398123,{"description":2932,"labels":2933,"number":2925,"owner":2877,"repository":2934,"state":2915,"title":2935,"updated_at":2936,"url":2937,"score":2930},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-5c4p72?file=test/default.test.ts\n\n### Describe the bug\n\n`@nuxt/test-utils` doesn't work with `jest` if one is to set it up in a way that Nuxt 3 documentation recommends (https://nuxt.com/docs/getting-started/testing#setup):\r\n\r\n```\r\n ● Test suite failed to run\r\n\r\n Returning a Promise from \"describe\" is not supported. Tests must be defined synchronously.\r\n\r\n 1 | import { setup } from '@nuxt/test-utils';\r\n 2 |\r\n > 3 | describe('Smoke test (default)', async () => {\r\n | ^\r\n 4 | await setup({});\r\n 5 |\r\n 6 | test('it goes well', async () => {\r\n\r\n at ErrorWithStack (node_modules/jest-util/build/ErrorWithStack.js:23:13)\r\n at Object.\u003Canonymous> (test/default.test.ts:3:9)\r\n at [object Object]\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],"test-utils","Using `@nuxt/test-utils` with `jest` results in `Returning a Promise from \"describe\" is not supported`","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/407",{"description":2939,"labels":2940,"number":2945,"owner":2877,"repository":2877,"state":2915,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.6.1\r\n- Nuxt Version: -\r\n- CLI Version: 3.10.0\r\n- Nitro Version: -\r\n- Package Manager: npm@10.1.0\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-f3bfuh?file=app.vue\r\n\r\n1. Open the reproduction in a new window\r\n2. Open the console\r\n3. TestComp.vue prints the div element, TestComp.client.vue prints undefined.\r\n\r\n### Describe the bug\r\n\r\nTemplate Refs are undefined in onMounted hook in client components.\r\n\r\n```vue\r\n// TestComp.client.vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst divRef = ref();\r\nonMounted(() => {\r\n console.log('onMounted');\r\n console.log(divRef.value); // undefined\r\n});\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv ref=\"divRef\" />\r\n\u003C/template>\r\n```\r\n\r\nThis components prints undefined in the console if its clientonly (it works if wrapped in ClientOnly but not if the file is .client.vue)\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2941,2944],{"name":2942,"color":2943},"3.x","29bc7f",{"name":2899,"color":2900},24398,"Template Refs are undefined in onMounted hook in *.client.vue components","2023-11-22T00:04:50Z","https://github.com/nuxt/nuxt/issues/24398",0.69417804,{"description":2951,"labels":2952,"number":2956,"owner":2877,"repository":2878,"state":2915,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2953,2954,2955],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.69651824,{"description":2962,"labels":2963,"number":2966,"owner":2877,"repository":2878,"state":2915,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\n-\n\n### Description\n\nDefault classes of container in [docs](https://ui3.nuxt.dev/components/container#theme) is:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\n**But no one of classes except `mx-auto` is not was created.**\nI change `--ui-container` variable like in [docs](https://ui3.nuxt.dev/getting-started/theme#container):\n```css\n/** app.css */\n\n@import 'tailwindcss';\n@import '@nuxt/ui';\n\n@theme {\n --container-xl: 1280px;\n}\n\n:root {\n --ui-container: var(--container-xl);\n}\n```\nAs result, container classes is `max-w-7xl mx-auto px-4 sm:px-6 lg:px-8` and still not was created, except `mx-auto`.\n\nBut if i create `app.config.ts`:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\nAll is ok, width and other classes are created and applying.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2964,2965],{"name":2868,"color":2869},{"name":2871,"color":2872},2655,"Classes of container component are not working properly","2024-11-16T13:13:33Z","https://github.com/nuxt/ui/issues/2655",0.69689095,{"description":2972,"labels":2973,"number":2976,"owner":2877,"repository":2877,"state":2915,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.19.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: css, extends, typescript, runtimeConfig, modules, directus\r\n- Runtime Modules: nuxt-directus@5.6.0\r\n- Build Modules: -\n\n### Reproduction\n\n`import { Ref } from 'vue';`\r\n`const testVar: Ref\u003Cany> = ref(null)`\n\n### Describe the bug\n\nHere is the error I get :\r\n`The requested module '/_nuxt/node_modules/.cache/vite/client/deps/vue.js?v=b0c30841' does not provide an export named 'Ref'`\r\nwhen I want to type my vars in vue components\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2974,2975],{"name":2942,"color":2943},{"name":2899,"color":2900},24653,"can't use type Ref without getting error","2023-12-13T09:14:53Z","https://github.com/nuxt/nuxt/issues/24653",0.70063555,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEr_ND40mnjiiB-5PWAnUgOGwMNoWyRLiAImA76EhkxI":-1},"/nuxt/nuxt.com/1336"]