\n\n\u003Cimg width=\"912\" height=\"578\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/71fb37a4-3959-413f-9076-74f63eee0108\" />\n\nNormal button:\n```html\n\u003CUButton\n color=\"info\"\n variant=\"soft\"\n size=\"xl\"\n icon=\"i-heroicons-question-mark-circle\"\n class=\"rounded-full\"\n aria-label=\"Show keyboard shortcuts\"\n />\n```\n\nIm using Nuxt4 and NuxtUI 3",[],416,"nuxt","icon","open","NuxtUI icons forced to width and height 1em!","2025-07-22T16:50:58Z","https://github.com/nuxt/icon/issues/416",0.7317981,{"description":3029,"labels":3030,"number":3031,"owner":3021,"repository":3032,"state":3023,"title":3033,"updated_at":3034,"url":3035,"score":3036},"I'm currently getting a lot of unnecessary tabs in `nuxt.config.ts`. For spaces, it works fine.\n\n\u003Cimg width=\"397\" height=\"357\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ccfb81cf-7f90-4f1d-ab85-6d6405dcf98c\" />",[],950,"cli","Support tabs for `npx nuxi@latest module add`","2025-07-10T11:29:02Z","https://github.com/nuxt/cli/issues/950",0.73437095,{"description":3038,"labels":3039,"number":3043,"owner":3021,"repository":3044,"state":3023,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nMinimal Reproduction - https://stackblitz.com/edit/github-remjha3q?file=app.vue\n\n- Open `app.vue` and `app.spec.ts` files\n- Open a new Terminal and run `npm run rest`\n\n### Describe the bug\n\nWhen testing a Vue component using `mountSuspended` from `@nuxt/test-utils/runtime`, computed properties fail to update reactively when their dependencies change. The same test cases pass when using `@vue/test-utils`' `mount` or `shallowMount` methods.\n\n## Current Behavior:\n- Data property `foo` updates correctly\n- Computed property `bar` remains stale with its initial value\n- Computed property `baz` remains stale with its initial value\n\n## Expected Behavior:\n- When `foo` changes to `true`:\n - `foo` property should update\n - `bar` should update to `\"(bar = true)\"`\n - `baz` should update to `\"baz => (bar = true)\"`\n\n## Workaround:\nUsing standard `@vue/test-utils` mounting methods works as expected:\n``` js\n// These alternatives work correctly\nreturn shallowMount(App, {});\n// or\nreturn mount(App, {});\n```\n\n## Files\n`package.json`\n```\n{\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\",\n \"test\": \"vitest\"\n },\n \"dependencies\": {\n \"nuxt\": \"^3.15.4\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"devDependencies\": {\n \"@nuxt/test-utils\": \"^3.15.4\",\n \"@vue/test-utils\": \"^2.4.6\",\n \"happy-dom\": \"^16.6.0\",\n \"jsdom\": \"^26.0.0\",\n \"vitest\": \"^3.0.5\"\n }\n}\n```\n\n`vitest.config.ts`\n```ts\nimport { defineVitestConfig } from '@nuxt/test-utils/config';\n\nexport default defineVitestConfig({\n test: {\n environment: 'nuxt',\n environmentOptions: {\n nuxt: {\n domEnvironment: 'jsdom', // 'happy-dom' (default) or 'jsdom'\n },\n },\n globals: true,\n },\n});\n```\n\n`app.vue`\n```vue\n\u003Ctemplate>\n \u003Cdiv>{{ baz }}\u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\">\nexport default defineNuxtComponent({\n name: 'UnitTestsMountSuspendedComputedValuesBug',\n\n data() {\n return {\n foo: false,\n };\n },\n\n computed: {\n bar() {\n return this.foo ? '(bar = true)' : '(bar = false)';\n },\n\n baz() {\n return 'baz => ' + this.bar;\n },\n },\n});\n\u003C/script>\n```\n\n`app.spec.ts`\n```ts\nimport { describe, beforeEach, it, expect } from 'vitest';\nimport { mountSuspended } from '@nuxt/test-utils/runtime';\nimport { shallowMount, mount } from '@vue/test-utils';\nimport App from './app.vue';\nimport { VueWrapper } from '@vue/test-utils';\n\nlet wrapper: VueWrapper\u003CInstanceType\u003Ctypeof App>>;\nconst mountComponent = async () => {\n // return shallowMount(App, { // this works as expected\n // return mount(App, { // this works as expected\n return await mountSuspended(App, { // this doesn't work as expected!\n // data() { // pre-setting data while using moutSuspended doesn't work as well! (it works fine with other methods though)\n // return {\n // foo: true,\n // };\n // },\n });\n};\n\ndescribe('AppMountSuspendedComputedValuesBug', () => {\n beforeEach(async () => {\n wrapper = await mountComponent();\n });\n\n // Toggling foo (data property) works as expected\n describe('foo', () => {\n it('should equal false by default', () => {\n expect(wrapper.vm.foo).toBe(false);\n });\n\n it('should equal true if changed using wrapper.vm.foo = true', async () => {\n wrapper.vm.foo = true;\n await wrapper.vm.$nextTick();\n expect(wrapper.vm.foo).toBe(true);\n });\n });\n\n // bar (coumputed value) doesn't update when foo (data property) changes\n describe('bar', () => {\n it('should return \"(bar = false)\" by default', () => {\n expect(wrapper.vm.bar).toBe('(bar = false)');\n });\n\n it('should return \"(bar = true)\" if this.foo === true', async () => {\n wrapper.vm.foo = true;\n await wrapper.vm.$nextTick();\n expect(wrapper.vm.bar).toBe('(bar = true)');\n });\n });\n\n // Obviously, baz (computed value) won't update becasue bar (computed value) doesn't update\n describe('baz', () => {\n it('should return \"baz => (bar = false)\" by default', () => {\n expect(wrapper.vm.baz).toBe('baz => (bar = false)');\n });\n\n it('should return \"baz => (bar = true)\" if this.foo === true', async () => {\n wrapper.vm.foo = true;\n await wrapper.vm.$nextTick();\n expect(wrapper.vm.baz).toBe('baz => (bar = true)');\n });\n });\n});\n```\n\n### Additional context\n\nPre-setting initial data values through the mount options also doesn't work with `mountSuspended`, while it works fine with other mounting methods.\n\n### Logs\n\n```shell-script\nRERUN app.spec.ts x1 \n\n ❯ app.spec.ts (6 tests | 2 failed) 234ms\n ✓ AppMountSuspendedComputedValuesBug > foo > should equal false by default\n ✓ AppMountSuspendedComputedValuesBug > foo > should equal true if changed using wrapper.vm.foo = true\n ✓ AppMountSuspendedComputedValuesBug > bar > should return \"(bar = false)\" by default\n × AppMountSuspendedComputedValuesBug > bar > should return \"(bar = true)\" if this.foo === true 44ms\n → expected '(bar = false)' to be '(bar = true)' // Object.is equality\n ✓ AppMountSuspendedComputedValuesBug > baz > should return \"baz => (bar = false)\" by default\n × AppMountSuspendedComputedValuesBug > baz > should return \"baz => (bar = true)\" if this.foo === true 36ms\n → expected 'baz => (bar = false)' to be 'baz => (bar = true)' // Object.is equality\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL app.spec.ts > AppMountSuspendedComputedValuesBug > bar > should return \"(bar = true)\" if this.foo === true\nAssertionError: expected '(bar = false)' to be '(bar = true)' // Object.is equality\n\nExpected: \"(bar = true)\"\nReceived: \"(bar = false)\"\n\n ❯ eval app.spec.ts:48:30\n 46| wrapper.vm.foo = true;\n 47| await wrapper.vm.$nextTick();\n 48| expect(wrapper.vm.bar).toBe('(bar = true)');\n | ^\n 49| });\n 50| });\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯\n\n FAIL app.spec.ts > AppMountSuspendedComputedValuesBug > baz > should return \"baz => (bar = true)\" if this.foo === true\nAssertionError: expected 'baz => (bar = false)' to be 'baz => (bar = true)' // Object.is equality\n\nExpected: \"baz => (bar = true)\"\nReceived: \"baz => (bar = false)\"\n\n ❯ eval app.spec.ts:61:30\n 59| wrapper.vm.foo = true;\n 60| await wrapper.vm.$nextTick();\n 61| expect(wrapper.vm.baz).toBe('baz => (bar = true)');\n | ^\n 62| });\n 63| });\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯\n\n\n Test Files 1 failed (1)\n Tests 2 failed | 4 passed (6)\n Start at 16:28:03\n Duration 730ms\n\n FAIL Tests failed. Watching for file changes...\n press h to show help, press q to quit\n```",[3040],{"name":3041,"color":3042},"pending triage","5D08F5",1115,"test-utils","Computed Properties Not Updating in Tests When Using mountSuspended","2025-03-05T13:12:03Z","https://github.com/nuxt/test-utils/issues/1115",0.7465844,{"description":3050,"labels":3051,"number":3057,"owner":3021,"repository":3021,"state":3023,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Describe the feature\n\nNuxt and its great, out-of-the-box DX are really enjoyable. However, I still prefer explicit imports over automatic ones, with exception for very well-known utilities and composables; such as the ones exposed by Vue's core.\n\nWhile configuring Nuxt to disable the auto-importing of almost everything, I noticed the API isn't really intuitive and could be improved. The problem is that in addition to having set `imports: { autoImport: false }`, we have to explicitly disable component auto-imports using `components: false` or `components: { dirs: [] }`. Even though everything is documented well, having to separately disable component auto-imports feels like an extra, not-really-obvious step. TBH, this isn't a big deal. However, things get worse when it comes to not just disabling auto-imports, but rather customizing it.\n\nI wanted to disable all auto-imports, and only have the presets of Vue & Vitest auto-imported. Unfortunately, the API isn't flexible enough to let me do something like this and call it a day:\n```ts\nimports: {\n autoImport: 'presets', // Boolean | 'presets'\n presets: ['vitest', /* Vue's preset seems to be included by default. */],\n},\n```\n\nSo, I came up with this solution by playing around with different `imports` hooks:\n```ts\n// Disable auto-importing custom components, composables, and utilities.\ncomponents: {\n dirs: [],\n},\nimports: {\n presets: ['vitest'],\n},\nhooks: {\n 'imports:extend': (imports) => {\n imports.length = 0;\n },\n}, \n```\n\n\u003Cbr />\nI'd really appreciate it if the team considers a more flexible and intuitive API.\n\n### Additional information\n\n- [ ] 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).",[3052,3055],{"name":3053,"color":3054},"enhancement","8DEF37",{"name":3041,"color":3056},"E99695",29275,"Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.7510992,{"description":3063,"labels":3064,"number":3071,"owner":3021,"repository":3072,"state":3073,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Description\n\nI am wondering what would be the best practise to have responsive tabs?\n\nAt the moment the default behavior is that the tabs truncate:\n\n\u003Cimg width=\"326\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b348656-5ae2-4b55-97c0-0f8bf16e621b\" />\n\nOn iphone SE this would be:\n\n\u003Cimg width=\"275\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7d9d49a8-6a22-47c6-8d29-7be2758c32e4\" />\n\nWould you not want them to kinda collaps or something? Thank you for some thoughts!",[3065,3068],{"name":3066,"color":3067},"question","d876e3",{"name":3069,"color":3070},"v3","49DCB8",4434,"ui","closed","UTabs: Responsiveness","2025-07-17T12:12:09Z","https://github.com/nuxt/ui/issues/4434",0.68350214,{"description":3079,"labels":3080,"number":3085,"owner":3021,"repository":3072,"state":3073,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.13\n- Builder: -\n- User Config: devtools, css, modules, runtimeConfig, compatibilityDate, i18n, auth, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.3, @sidebase/nuxt-auth@0.10.1, @nuxtjs/i18n@9.5.5, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nNuxt UI 3: https://codesandbox.io/p/devbox/winter-cherry-2pwhgv\nNuxt UI 2: https://stackblitz.com/edit/nuxt-ui-w6xry7tp?file=app.vue\n\n### Description\n\nI'm migrating my app from Nuxt UI 2 to 3. This is a regression in the Nuxt UI 3 version.\n\nIf this isn't possible, can we have a tooltip or something?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3081,3084],{"name":3082,"color":3083},"bug","d73a4a",{"name":3069,"color":3070},4300,"Select should expand to item's full width or at least allow showing it","2025-06-11T09:09:13Z","https://github.com/nuxt/ui/issues/4300",0.7017462,{"description":3091,"labels":3092,"number":3095,"owner":3021,"repository":3072,"state":3073,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Environment\n\n\"@vueuse/nuxt\": \"^13.1.0\"\n\"@nuxt/ui\": \"^3.1.2\"\nnode: lts/jod (22.11.0)\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\n\n\n\n\n### Description\n\nWhen using the UTab component with the variant=\"link\", applying custom CSS classes to enable horizontal scrolling (e.g., overflow-x: auto; or equivalent utility classes) causes the visual style indicating the currently active tab to be lost or overridden.\n\n```js\n{\n variant: 'link',\n ui: {\n list: 'bg-white overflow-x-auto overflow-y-hidden',\n trigger: 'min-w-auto'\n }\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3093,3094],{"name":3082,"color":3083},{"name":3069,"color":3070},4198,"UTabs style issue","2025-05-23T13:23:24Z","https://github.com/nuxt/ui/issues/4198",0.70666236,{"description":3101,"labels":3102,"number":3112,"owner":3021,"repository":3072,"state":3073,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.2\n- Nuxt Version: 3.13.0\n- CLI Version: 3.13.0\n- Nitro Version: 2.9.7\n- Package Manager: yarn@3.7.0\n- Builder: -\n- User Config: app, modules, algolia, content, fonts, colorMode, tailwindcss, site, schemaOrg, nitro, runtimeConfig, sourcemap, experimental, compatibilityDate\n- Runtime Modules: @nuxt/content@2.13.2, @nuxt/image@1.7.0, @nuxt/ui@2.18.4, @nuxt/fonts@0.6.1, nuxt-og-image@3.0.0-rc.65, @nuxtjs/algolia@1.10.2, nuxt-schema-org@2.2.0\n- Build Modules: -\n------------------------------\n\n### Version\n\nv2.18.3\n\n### Reproduction\n\n1. Go to https://ui.nuxt.com/components/tabs?tab=Tab1#control-the-selected-index\n\n2. Click on any tab that is not tab 1 (`tabs?tab=Tab3#control-the-selected-index`)\n\n3. Copy the link to that tab and paste it in a new browser tab or reload page\n4. The tab is not rendered correctly\n\n\n\n\n### Description\n\nLinks to the tabs don't work correctly, they don't render at all\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3103,3104,3107,3110],{"name":3082,"color":3083},{"name":3105,"color":3106},"triage","ffffff",{"name":3108,"color":3109},"closed-by-bot","ededed",{"name":3111,"color":3109},"stale",2356,"[Tabs] Tabs don't render correctly, even on the documentation page","2025-06-18T09:05:59Z","https://github.com/nuxt/ui/issues/2356",0.7364685,{"description":3118,"labels":3119,"number":3123,"owner":3021,"repository":3072,"state":3073,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Description\r\n\r\nThe code for specifying column width when there is no data is as follows and it is expected\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUTable :empty-state=\"{ icon: 'i-heroicons-circle-stack-20-solid', label: 'No items.' }\" :rows=\"people\"\r\n :columns=\"columns\">\r\n \u003Ctemplate #from-data=\"{ row }\">\r\n {{ row.from.value }}\r\n \u003C/template>\r\n \u003C/UTable>\r\n \u003CUNotifications>\r\n \u003Ctemplate #title=\"{ title }\">\r\n \u003Cspan v-html=\"title\" />\r\n \u003C/template>\r\n\r\n \u003Ctemplate #description=\"{ description }\">\r\n \u003Cspan v-html=\"description\" />\r\n \u003C/template>\r\n \u003C/UNotifications>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst toast = useToast()\r\nconst app = useNuxtApp()\r\n\r\nconst columns = [{\r\n key: \"id\",\r\n label: \"编号\",\r\n class: 'w-16'\r\n}, {\r\n key: \"from\",\r\n label: \"发方\",\r\n class: 'w-[180px]'\r\n}, {\r\n key: \"to\",\r\n label: \"接方\",\r\n class: 'w-[180px]'\r\n\r\n}, {\r\n key: \"type\",\r\n label: \"类型\",\r\n class: 'w-[120px]'\r\n\r\n}, {\r\n key: \"value\",\r\n label: \"金额\",\r\n class: 'w-[120px]'\r\n\r\n}, {\r\n key: \"hash\",\r\n label: \"哈希\",\r\n}\r\n]\r\n\r\nconst people = ref([\r\n /*{\r\n \"id\": 1,\r\n \"from\": { value: '0x11111111fce9647bdf1e7877bf73ce8b0bad1111', class: 'w-[80px]' },\r\n \"to\": '0x22222222fce9647bdf1e7877bf73ce8b0bad2222',\r\n \"type\": 'ETH',\r\n \"value\": '123',\r\n \"hash\": '0x88baba17ca0060d644a72a9460260104eea81e7959445d3500d015ed71875d38',\r\n }*/\r\n])\r\n\r\n\r\n\u003C/script>\r\n\r\n\r\n\u003Cstyle>\r\na {\r\n color: #65a30d;\r\n font-weight: 700;\r\n font-size: 20px;\r\n}\r\n\r\n\r\n\u003C/style>\r\n```\r\n\r\n\r\n\r\nHowever, once there is data, it will be stretched open. How can I fix the header so that the content is partially hidden and drag the header to decide whether to hide or display it? This is too common in daily development and provides a good user experience\r\n\r\n\r\n```vue\r\nconst people = ref([\r\n {\r\n \"id\": 1,\r\n \"from\": { value: '0x11111111fce9647bdf1e7877bf73ce8b0bad1111', class: 'w-[80px]' },\r\n \"to\": '0x22222222fce9647bdf1e7877bf73ce8b0bad2222',\r\n \"type\": 'ETH',\r\n \"value\": '123',\r\n \"hash\": '0x88baba17ca0060d644a72a9460260104eea81e7959445d3500d015ed71875d38',\r\n }\r\n])\r\n```\r\n\r\n",[3120,3121,3122],{"name":3066,"color":3067},{"name":3108,"color":3109},{"name":3111,"color":3109},2092,"UTable column width","2025-06-18T09:06:18Z","https://github.com/nuxt/ui/issues/2092",0.74257106,{"description":3129,"labels":3130,"number":3043,"owner":3021,"repository":3136,"state":3073,"title":3137,"updated_at":3138,"url":3139,"score":3048},"Duplicate the support offer as displayed on nuxt.com landing page (see pic below) on nuxtjs.org \n\n\nand update NEN description with \"A network of experienced freelancers, officially certified by Nuxtlabs' lead engineers and all contributors to Nuxt OS projects\" + put capital letter on \"Nuxt Experts Network\"",[3131,3133],{"name":3053,"color":3132},"1ad6ff",{"name":3134,"color":3135},"marketing","f5c828","nuxt.com","[Landing Nuxtjs.org] include support offers on nuxtjs.org landing page","2023-10-03T13:46:53Z","https://github.com/nuxt/nuxt.com/issues/1115",["Reactive",3141],{},["Set"],["ShallowReactive",3144],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZdecle0AcMrppnqMu4f8gJwKqYKZwROIjCh6vRwHjtc":-1},"/nuxt/ui/4056"]