\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```",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"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.7052828,{"description":2880,"labels":2881,"number":2885,"owner":2872,"repository":2886,"state":2874,"title":2887,"updated_at":2888,"url":2889,"score":2890},"Hey there!\n\nI have been recently looking at the nuxt modules page and I really like the fact that certain modules have `official` badge. Maybe we could do something similar for modules that are hosted in `@nuxtjs` with label `community` or `ecosystem`?\n\nCurrent:\n\n\nAfter this change:\n\n\n\nDo you think it makes sense? :)\n\nI can create a draft PR if you like to see how it works in details",[2882],{"name":2883,"color":2884},"enhancement","1ad6ff",1723,"nuxt.com","Label for community modules","2024-12-04T08:48:56Z","https://github.com/nuxt/nuxt.com/issues/1723",0.7328438,{"description":2892,"labels":2893,"number":2897,"owner":2872,"repository":2898,"state":2874,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### Environment\n\nWorking directory: /home/olada/nuxt-starter-ebey3puz nuxi 00:02:27\nNuxt project info: nuxi 00:02:27\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools, pages, modules\n- Runtime Modules: @nuxt/test-utils/module@3.17.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/olada/nuxt-starter-ebey3puz\n\nRun `pnpm test` (automatically run when opening the reproduction)\n\n### Describe the bug\n\nI have attempted to write a test for a plugin I have written.\n\nI was surprised to find that vitest shows an error message that no test suite can be found\n\n```\n❯ plugins/customFetch.nuxt.spec.ts (0 test)\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL plugins/customFetch.nuxt.spec.ts [ plugins/customFetch.nuxt.spec.ts ]\nError: No test suite found in file /home/olada/nuxt-starter-ebey3puz/plugins/customFetch.nuxt.spec.ts\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\n\n\n Test Files 1 failed (1)\n Tests no tests\n Start at 00:01:38\n Duration 506ms\n\n FAIL Tests failed. Watching for file changes...\n press h to show help, press q to quit\nCancelling test run. Press CTRL+c again to exit forcefully.\n\n ELIFECYCLE Test failed. See above for more details.\n```\n\nWhen renaming the folder \"plugins\" to e.g. \"pluginss\" or when moving the file /plugins/customFetch.spec.ts to /plugins/\\_\\_tests\\_\\_/customFetch.spec.ts the tests are correctly picked up.\n\nIt seems that nuxt somehow interferes with the test strategy of placing the tests into the very same directory as the \"live code\".\n\nAs a side note: Nuxt detects the spec file as a plugin and renders a warning that no default export was found inside of the .spec. file. \n```\n[warn] [nuxt] Plugin `/home/olada/nuxt-starter-ebey3puz/plugins/customFetch.nuxt.spec.ts` has no default export and will be ignored at build time. Add `export default defineNuxtPlugin(() => {})` to your plugin.\n```\n\nMaybe the fact that Nuxt interpretes spec-files as a real plugin is related to the whole \"no test suite found\" issue?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nRERUN plugins/customFetch.nuxt.spec.ts x1 \n\n[warn] [nuxt] Plugin `/home/olada/nuxt-starter-ebey3puz/plugins/customFetch.nuxt.spec.ts` has no default export and will be ignored at build time. Add `export default defineNuxtPlugin(() => {})` to your plugin.\n ❯ plugins/customFetch.nuxt.spec.ts (0 test)\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL plugins/customFetch.nuxt.spec.ts [ plugins/customFetch.nuxt.spec.ts ]\nError: No test suite found in file /home/olada/nuxt-starter-ebey3puz/plugins/customFetch.nuxt.spec.ts\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\n\n\n Test Files 1 failed (1)\n Tests no tests\n Start at 00:01:38\n Duration 506ms\n\n FAIL Tests failed. Watching for file changes...\n press h to show help, press q to quit\nCancelling test run. Press CTRL+c again to exit forcefully.\n\n ELIFECYCLE Test failed. See above for more details.\n\n~/olada/nuxt-starter-ebey3puz main 5m 37s\n❯ npx nuxi info\nWorking directory: /home/olada/nuxt-starter-ebey3puz nuxi 00:02:09\nNuxt project info: nuxi 00:02:09\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools, pages, modules\n- Runtime Modules: @nuxt/test-utils/module@3.17.2\n- Build Modules: -\n------------------------------\n\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\n👉 Read documentation: https://nuxt.com\n\n\n~/olada/nuxt-starter-ebey3puz main 2s\n❯ pnpx nuxi info\nPackages: +1\n+\nProgress: resolved 1, reused 0, downloaded 1, added 1, done\nWorking directory: /home/olada/nuxt-starter-ebey3puz nuxi 00:02:27\nNuxt project info: nuxi 00:02:27\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools, pages, modules\n- Runtime Modules: @nuxt/test-utils/module@3.17.2\n- Build Modules: -\n------------------------------\n\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\n👉 Read documentation: https://nuxt.com\n```",[2894],{"name":2895,"color":2896},"pending triage","5D08F5",1203,"test-utils","No test suite found inside of \"plugins\" folder","2025-03-26T23:50:01Z","https://github.com/nuxt/test-utils/issues/1203",0.7343088,{"description":2904,"labels":2905,"number":2911,"owner":2872,"repository":2873,"state":2874,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, nuxt-auth-sanctum@0.5.2, @vueuse/nuxt@11.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.14.1592\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst places = ref([])\nconst placeItems = ref([{ id: 1, name: 'Place 1' }, { id: 2, name: 'Place 2' }])\n\u003C/script>\n\n\u003Ctemplate>\n\u003CUInputMenu name=\"places\"\n v-model=\"places\"\n :items=\"placeItems\"\n value-key=\"id\"\n label-key=\"name\"\n icon=\"i-lucide-search\"\n class=\"w-full\"\n multiple/>\n\u003C/template>\n```\n\n\n\n\n\n### Description\n\nName attribute should be `name[]`, not `[name][]`.",[2906,2907,2910],{"name":2866,"color":2867},{"name":2908,"color":2909},"v3","49DCB8",{"name":2869,"color":2870},2740,"UInputMenu has wrong name attribute when multiple active","2024-11-23T20:48:26Z","https://github.com/nuxt/ui/issues/2740",0.735774,{"description":2917,"labels":2918,"number":2919,"owner":2872,"repository":2920,"state":2874,"title":2921,"updated_at":2922,"url":2923,"score":2924},"It would be nice if you could alias and entire collection instead of just an icon.\n\nRight now I do it this way.\n```ts\nconst createIconAliases = (newPrefix: string, iconifyJson: IconifyJSON) => {\n const exisitngPrefix = iconifyJson.prefix;\n const icons = Object.keys(iconifyJson.icons);\n\n return icons.reduce(\n (object, value) => {\n object[`${newPrefix}:${value}`] = `${exisitngPrefix}:${value}`;\n return object;\n },\n {} as Record\u003Cstring, string>,\n );\n};\n```",[],362,"icon","[feature request] Allow aliasing entire collection","2025-02-21T20:10:51Z","https://github.com/nuxt/icon/issues/362",0.73733956,{"description":2926,"labels":2927,"number":2936,"owner":2872,"repository":2898,"state":2874,"title":2937,"updated_at":2938,"url":2939,"score":2940},"Hey, firstly thank you for making this plugin, it looks very useful :)\r\n\r\nRunning this module seems to run the whole nuxt environment, including the plugins, and we have a plugin that makes a api call. We normally just mock the module where we import the api function but it doesn't seem to work in this case. For example:\r\n```\r\n// somePlugin.ts\r\nimport { fetchProducts } from \"~/service/products\";\r\n\r\nexport default defineNuxtPlugin(async () => {\r\n const products = fetchProducts();\r\n // do something with the products\r\n});\r\n```\r\n\r\n```\r\n// SomeComponent.nuxt.spec.js\r\nimport { describe, it, expect, vi } from \"vitest\";\r\nimport { shallowMount } from \"@vue/test-utils\";\r\nimport SomeComponent from \"../SomeComponent.vue\";\r\n\r\n// trying to mock the products service so that the real api doesn't get called during the plugins\r\nvi.mock(\"~/service/products\");\r\n\r\ndescribe(\"SomeComponent\", async () => {\r\n it(\"Is a Vue instance\", () => {\r\n const wrapper = shallowMount(SomeComponent);\r\n expect(wrapper.vm).toBeTruthy();\r\n });\r\n});\r\n```\r\n\r\nI assume these mocks only work for the component that we are testing and not for the plugins in the nuxt environment for example. Do you have a suggestion about how to solve this?",[2928,2931,2933],{"name":2929,"color":2930},"documentation","0075ca",{"name":2883,"color":2932},"a2eeef",{"name":2934,"color":2935},"vitest-environment","b60205",544,"mocking plugins used within nuxt","2024-07-23T12:17:21Z","https://github.com/nuxt/test-utils/issues/544",0.7424412,{"description":2942,"labels":2943,"number":2946,"owner":2872,"repository":2873,"state":2874,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.11.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.6\n- Package Manager: pnpm@9.5.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@8.0.0, @nuxt/ui@2.16.0, @nuxtjs/tailwindcss@6.12.0, @pinia/nuxt@0.5.1, @nuxtjs/google-fonts@3.2.0, @nuxtjs/eslint-module@4.1.0, @nuxt/test-utils/module@3.13.1\n- Build Modules: -\n------------------------------\n\n\n\n### Version\n\nv.2.15.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1f7znf?file=app.vue,nuxt.config.ts\n\n### Description\n\nWhen providing custom animations through tailwindcss config, some Nuxt UI animations stop working. I have provided an example of a `UButton` with `loading` set in the repro link above.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2944,2945],{"name":2866,"color":2867},{"name":2869,"color":2870},2732,"Adding custom animations disable Nuxt UI ones","2024-11-22T15:38:35Z","https://github.com/nuxt/ui/issues/2732",0.7429035,{"description":2952,"labels":2953,"number":2958,"owner":2872,"repository":2873,"state":2959,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### 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```",[2954,2957],{"name":2955,"color":2956},"question","d876e3",{"name":2908,"color":2909},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.69396085,{"description":2965,"labels":2966,"number":2969,"owner":2872,"repository":2873,"state":2959,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### 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_",[2967,2968],{"name":2866,"color":2867},{"name":2908,"color":2909},2349,"UInput causes error","2024-10-10T14:15:25Z","https://github.com/nuxt/ui/issues/2349",0.69812226,{"description":2975,"labels":2976,"number":2979,"owner":2872,"repository":2873,"state":2959,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### 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```",[2977,2978],{"name":2866,"color":2867},{"name":2908,"color":2909},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.7107268,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxZ5j7XLdEEe218xFpyETHs6LZJRCCD5SZ_kpxDeHaU8":-1},"/nuxt/ui/2365"]