\n \u003C/template>\n \u003Cv-list v-model:selected=\"selected\" selectable density=\"default\" max-height=\"40vh\" select-strategy=\"leaf\">\n \u003Ctemplate v-for=\"item in items\" :key=\"item.title\">\n \u003Cv-list-item>\n {{ item.title }}\n \u003C/v-list-item>\n \u003C/template>\n \u003C/v-list>\n \u003C/v-menu>\n\u003C/template>\n\n\u003Cscript lang=\"ts\">\nimport { defineComponent, reactive, ref } from 'vue'\n\nexport default defineComponent({\n name: 'AppTestComponent',\n setup() {\n const selected = ref([])\n const menuShow = ref(false)\n return {\n menuShow,\n selected,\n }\n },\n computed: {\n items() {\n return [\n {\n title: 'My Title',\n },\n ]\n },\n },\n})\n\u003C/script>\n```\n\ntest\n\n```typescript\n\nimport { describe, expect, test } from 'vitest'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport AppTestComponent from '~/components/AppTestComponent.vue'\nimport { mount } from '@vue/test-utils'\nimport { VList } from 'vuetify/components/VList'\n\ndescribe('AppTestComponent', () => {\n test('renders', async () => {\n const component = mount(AppTestComponent)\n\n await component.find('button').trigger('click')\n const listContent = component.findComponent(VList).html()\n expect(listContent).toContain('My Title')\n })\n test('will fail', async () => {\n const component = await mountSuspended(AppTestComponent)\n\n await component.find('button').trigger('click')\n const listContent = component.findComponent(VList).html()\n expect(listContent).toContain('My Title')\n })\n})\n\n```\n\n\n### Describe the bug\n\n\nWhen testing Vuetify components with `mountSuspended` from `@nuxt/test-utils/runtime`, I discovered that ref values are not properly unwrapped before being passed to components.\n\nSpecifically, when mounting Vuetify's `VMenu` or `VList` components, props like `modelValue` (for VMenu) or `selected` (for VList) receive the actual ref object instead of the ref's value. This behavior differs from Vue Test Utils' standard `mount` function, which correctly unwraps ref values.\n\n## Reproduction Steps\n\nThe issue occurs when:\n1. Using `mountSuspended` from `@nuxt/test-utils/runtime`\n2. Testing components created with `defineComponent()`\n3. Passing refs as props to Vuetify components from `setup()`\n\nInterestingly, components using `\u003Cscript setup>` syntax work correctly.\n\n## Error Details\n\nThe error occurs in Vuetify's internal code when it tries to iterate over what it expects to be an array value but receives a ref object instead:\n\n```\nTypeError: (v || []) is not iterable\n ❯ Object.in node_modules/vuetify/src/composables/nested/selectStrategies.ts:56:25\n ❯ transformIn node_modules/vuetify/src/composables/nested/nested.ts:184:33\n ❯ ComputedRefImpl.get [as fn] node_modules/vuetify/src/composables/proxiedModel.ts:53:14\n ❯ refreshComputed node_modules/@vue/reactivity/dist/reactivity.cjs.js:384:28\n ❯ ComputedRefImpl.value node_modules/@vue/reactivity/dist/reactivity.cjs.js:1625:5\n ❯ ComputedRefImpl.fn node_modules/vuetify/src/composables/nested/nested.ts:356:53\n ❯ refreshComputed node_modules/@vue/reactivity/dist/reactivity.cjs.js:384:28\n ❯ ComputedRefImpl.value node_modules/@vue/reactivity/dist/reactivity.cjs.js:1625:5\n ❯ ComputedRefImpl.fn node_modules/vuetify/src/components/VList/VListItem.tsx:141:105\n ❯ refreshComputed node_modules/@vue/reactivity/dist/reactivity.cjs.js:384:28\n```\n\n## Investigation Findings\n\nWhen debugging the Vuetify components by placing breakpoints in their setup functions, I observed that:\n- With `@vue/test-utils` mount: Props contain the actual values of refs\n- With `@nuxt/test-utils` mountSuspended: Props contain the ref objects themselves\n\nI suspect this is related to how `mountSuspended` handles the return value of `setup()` when using `defineComponent()`, failing to properly unwrap reactive references before passing them as props.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2920],{"name":2921,"color":2922},"pending triage","5D08F5",1199,"test-utils","Component props are passed as ref instead of refs value when using defineComponent()","2025-03-20T22:07:30Z","https://github.com/nuxt/test-utils/issues/1199",0.8036853,{"description":2930,"labels":2931,"number":2940,"owner":2910,"repository":2910,"state":2912,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### Describe the feature\n\n* Related https://github.com/nuxt-modules/i18n/issues/2411\r\n* Blocks https://github.com/nuxt-modules/i18n/pull/2408\r\n\r\nIn [`@nuxtjs/i18n (v8)`](https://github.com/nuxt-modules/i18n) we manually sync the implementation of `parseSegment` and `getRoutePath` as these are not exported. Not sure if exporting as is, or in `@nuxt/kit`, or elsewhere would make more sense.\n\n### Additional information\n\n- [X] 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).",[2932,2934,2937],{"name":2904,"color":2933},"8DEF37",{"name":2935,"color":2936},"kit","60E14C",{"name":2938,"color":2939},"🍰 p2-nice-to-have","0E8A16",23521,"Export page utility functions","2024-06-30T11:07:24Z","https://github.com/nuxt/nuxt/issues/23521",0.8080775,{"description":2946,"labels":2947,"number":2948,"owner":2910,"repository":2949,"state":2950,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Environment\n\nDocumentation \n\n### Reproduction\n\nThis error happens on a mobile phone using Firefox \r\n* go to the modules page: https://nuxt.com/modules\r\n* scroll down to one of the lower modules\r\n* go to a module page (for instance, go to the \"lodash\" module)\r\n* use the back button, or back-guesture\r\n* see that your scroll position is now at \"eslint\" (the first module in the list) and not at \"lodash\".\n\n### Describe the bug\n\nAfter navigating back to the modules page, your original scroll position is not remembered.\n\n### Additional context\n\nThis is on my mobile phone. I did not try on desktop.\n\n### Logs\n\n_No response_",[],1313,"nuxt.com","closed","Back navigation on modules page in documentation does not remember scroll position","2023-10-10T14:44:49Z","https://github.com/nuxt/nuxt.com/issues/1313",0.7478912,{"description":2956,"labels":2957,"number":2958,"owner":2910,"repository":2959,"state":2950,"title":2960,"updated_at":2961,"url":2962,"score":2963},"\r\n\r\n\r\n\r\n\r\n\r\n这是下面遇到的问题:\r\n\r\n\r\n\r\n",[],258,"icon","After packaging, I don't know why it points to https://api.iconify.design/icon.json. This will return 404, causing the website icon svg to not come out. The following is my nuxt.config configuration. I don't want to request https://api.iconify.design/icon.json because it is my local icon.","2024-09-22T21:35:12Z","https://github.com/nuxt/icon/issues/258",0.7696185,{"description":2965,"labels":2966,"number":2969,"owner":2910,"repository":2911,"state":2950,"title":2970,"updated_at":2971,"url":2972,"score":2973},"Todo after #2298 is merged",[2967,2968],{"name":2904,"color":2905},{"name":2907,"color":2908},2314,"Handle dynamic `--radius` token","2024-10-09T12:28:47Z","https://github.com/nuxt/ui/issues/2314",0.7830889,{"description":2975,"labels":2976,"number":2980,"owner":2910,"repository":2911,"state":2950,"title":2981,"updated_at":2982,"url":2983,"score":2984},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nIs there any way to use [Headless UI CSS modifiers](https://headlessui.com/v1/vue/disclosure#using-data-attributes) in a Nuxt app, `ui-open`, to control the set of css classes?\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { Disclosure, DisclosureButton, DisclosurePanel } from '@headlessui/vue';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CDisclosure>\n \u003CDisclosureButton>\n \u003Cdiv class=\"text-red-500 ui-open:text-cyan-700\">Button\u003C/div>\n \u003C/DisclosureButton>\n \u003CDisclosurePanel>Text\u003C/DisclosurePanel>\n \u003C/Disclosure>\n \u003C/div>\n\u003C/template>\n```",[2977],{"name":2978,"color":2979},"question","d876e3",2715,"Using Headless UI CSS modifiers inside Nuxt app","2024-11-21T17:07:05Z","https://github.com/nuxt/ui/issues/2715",0.7843558,{"description":2986,"labels":2987,"number":2988,"owner":2910,"repository":2949,"state":2950,"title":2989,"updated_at":2990,"url":2991,"score":2992},"\n",[],1007,"docs/api/composables/use-nuxt-app#callhookname-args: Missing Space ","2023-10-10T14:45:30Z","https://github.com/nuxt/nuxt.com/issues/1007",0.7901702,{"description":2994,"labels":2995,"number":3002,"owner":2910,"repository":2910,"state":2950,"title":3003,"updated_at":3004,"url":3005,"score":3006},"## Motivation\r\n\r\nVue is a very international community with a lot of presence in non-english regions like China.\r\n\r\n- Many community members have proposed their help here https://github.com/nuxt/nuxt/discussions/16054\r\n- China have a (non-official ?) Chinese version of the Nuxt docs https://github.com/nuxt/nuxt/discussions/16208 : https://nuxt.com.cn/\\\r\n- A Russian translation has been discussed https://github.com/nuxt/nuxt/discussions/17351\r\n- A Ukrainian translation have been discussed https://github.com/nuxt/nuxt/issues/19926\r\n\r\nFormkit recently released an AI translation for their website docs https://formkit.com/ in 4 languages. \r\n\r\nWe could take a similar approach and combine it with the existing community translations.\r\nIn my opinion, an AI approach needs to be compatible with existing contributions, and manual modifications.\r\n\r\n## Implementation idea\r\n\r\n*Disclaimer: I'm sharing some of my thoughts about how we could build such a system, to gauge community interest in doing so. Suggestion and feedback would be very appreciated!*\r\n\r\nWe would use i18n for the docs website to handle the language strings (related docus issue https://github.com/nuxt-themes/docus/issues/770)\r\nThen to keep the translations in sync with the english source, we could run logic (maybe within the CI), that is triggered when english docs gets merged in nuxt/nuxt, and automatically open PRs for each language with a LLM translation inserted at the right location. \r\nWith such a system, the Nuxt community/team can review the LLM output and modify it before merging it for their language. \r\nAll new additions to the docs must be done in English, so that they are reflected anywhere.\r\nIf translations PRs are an issue for maintainers, we could move all of this to another repo `nuxt-international` or something.\r\n\r\nMany of the Nuxt/Unjs team members already speak 2 or more languages, so we could start out with these languages.\r\nIf this system is successful, it can be expanded and applied to other things, such as the UnJS ecosystem, or integrated with docus\r\n\r\n### Create entire translations from scratch\r\n\r\nWhile working from human written translation is more accurate, we could also experiment with entirely AI written translations. We could build a tool that translates all markdown docs content from the english source into a new language.\r\n\r\n## Bonus\r\n\r\nLook at worldwide trends for Nuxt over the last year : https://trends.google.com/trends/explore?q=nuxt,nuxtjs,nuxt.js&hl=en-GB\r\n\r\nInterestingly enough, there's more search interest for Nuxt in China than in english speaking countries.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/98146ec6-c6d7-479d-afb9-bcb7ee13bf4f\">\r\n\r\nIn fact, the anglosphere rank significantly lower than other areas.\r\n\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2996,2999],{"name":2997,"color":2998},"documentation","5319e7",{"name":3000,"color":3001},"discussion","538de2",21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.79224664,{"description":3008,"labels":3009,"number":3019,"owner":2910,"repository":2949,"state":2950,"title":3020,"updated_at":3021,"url":3022,"score":3023},"_Add the Enterprise page from the new Support/Solutions page made by @SarahM19 and @FerdinandCoumau _",[3010,3013,3016],{"name":3011,"color":3012},"design","00bd6f",{"name":3014,"color":3015},"marketing","f5c828",{"name":3017,"color":3018},"dev","018415",1345,"Enterprise Page","2023-10-10T14:44:54Z","https://github.com/nuxt/nuxt.com/issues/1345",0.79410803,["Reactive",3025],{},["Set"],["ShallowReactive",3028],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fogpoGRw5azNGHucUIGB0oIaHsmt2IgKCLu2ePY9sCTY":-1},"/nuxt/ui/3805"]