\n```\n\nAfter:\n```html\n\u003C!-- `ui` prop is the same as `app.config.ts` theming config\n\u003CUTheme :ui=\"{\n formField: {\n\t slots: {\n\t root: \"flex max-sm:flex-col justify-between items-center gap-4\",\n\t},\n },\n}\">\n \u003CUForm ...>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUForm/>\n\u003C/UTheme>\n```\n\n## Benefits\n- Easily componentized. I could create a `AppForm` component which contains the `UTheme` usage with a slot, so now its 1 line to get the exact theming that I want. This makes consistency across the app really easy.\n- Nestable - If implemented with provide/inject, you could have an infinite number of UTheme's nested and it would take the latest one\n\n## Implementation\nI'd tentatively be willing to implement this. My approach would be:\n- Create `UTheme`, it should have a `ui` and `uiPro` prop, each of which take the same type as the `app.config.ts`\n- `provide()` those props\n- `inject()` those props into each component and merge with passed in `ui` field.\n- Theme priority order should be:\n 1. `ui` prop passed to component\n 2. `ui` prop coming from UTheme component\n 3. `ui` config coming from `app.config.ts`\n\n### Additional context\n\n_No response_",[3170,3171,3172],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4250,"UTheme component","2025-05-28T22:24:36Z","https://github.com/nuxt/ui/issues/4250",0.76262534,{"description":3179,"labels":3180,"number":3186,"owner":3147,"repository":3148,"state":3187,"title":3188,"updated_at":3189,"url":3190,"score":3191},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.1\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.42\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/i18n@9.1.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nV3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-forked-lz4ygf\n\n### Description\n\nOnce a USelectMenu is placed inside of a USlideover, the search breaks. You can't highlight the search input, you can still select items without a problem.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3181,3182,3185],{"name":3158,"color":3159},{"name":3183,"color":3184},"duplicate","cfd3d7",{"name":3141,"color":3142},3021,"closed","USelectMenu search breaks when placed inside of a USlideover","2025-01-25T12:43:16Z","https://github.com/nuxt/ui/issues/3021",0.74021035,{"description":3193,"labels":3194,"number":3201,"owner":3147,"repository":3147,"state":3187,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Environment\n\nNuxi 3.3.3 16:40:34\r\n 16:40:35\r\nRootDir: C:/Users/d91589/Desktop/Projects/onlylaw/frontend-nuxt 16:40:35\r\nNuxt project info: 16:40:35\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@9.6.2`\r\n- Builder: `vite`\r\n- User Config: `imports`, `typescript`, `modules`, `runtimeConfig`, `experimental`, `vite`, `css`, `i18n`, `pinia`\r\n- Runtime Modules: `@nuxtjs/i18n@8.0.0-beta.10`, `@vueuse/nuxt@9.13.0`, `@pinia/nuxt@0.4.6`, `@nuxtjs/device@3.1.0`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nProblem is clear from description\n\n### Describe the bug\n\nI use \r\n```\r\ndefinePageMeta({\r\n layout: \"layoutname\",\r\n});\r\n```\r\n to change the layout for different pages. \r\n\r\nFirst layout: \r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CLayoutHeader>\u003C/LayoutHeader>\r\n \u003Cslot>\u003C/slot>\r\n \u003CLayoutFooter>\u003C/LayoutFooter>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nSecond layout: \r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CLayoutHeader>\u003C/LayoutHeader>\r\n \u003Cslot>\u003C/slot>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nWhen I change the layout, the header component rerenders. I think components that already exist in a layout should not be rerendered. Is that a bug or expected behavior?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3195,3198],{"name":3196,"color":3197},"3.x","29bc7f",{"name":3199,"color":3200},"pending triage","E99695",21062,"Changing layout rerenders existing layout components","2023-05-25T16:05:23Z","https://github.com/nuxt/nuxt/issues/21062",0.74207133,{"description":3207,"labels":3208,"number":3212,"owner":3147,"repository":3148,"state":3187,"title":3213,"updated_at":3214,"url":3215,"score":3216},"Related #196 \n\n| Alias | Name | Version |\n| ----- | ------------------------------------------- | --------------- |\n| ui | [nuxt/ui][nuxt-ui-href] | v3.0.0-alpha.10 |\n| tw | [tailwindcss][tailwindcss-href] | v4.0.0-beta.8 |\n| tv | [tailwind-variants][tailwind-variants-href] | v0.3.0 |\n| tm | [tailwind-merge][tailwind-merge-href] | v2.6.0 |\n| uno | [unocss][unocss-href] | v0.65.3 |\n\n**ui internally uses tv to flexibly generate component class names. tv internally uses tm to merge classes with the same effect (e.g., `p-2 p-4` --> `p-4`), and finally uses tw to recognize class names and generate style classes.**\n\n**After examining tv and tm, it became apparent that they don't strongly depend on tw, which opens up the possibility of replacing the final style generation step with uno.**\n\n\u003Cdetails>\n\u003Csummary>## tw Prefix Attempt (Optional)\u003C/summary>\n\nInitially, the idea was to limit tw to ui internals and uno for user usage. With tw's [prefix][tw-prefix-href] feature, the class rules became simpler. **However, ui internally (v3.0.0-alpha.10) doesn't yet support passing tw prefix configuration**, so let's first make ui support tw prefixes.\n\n### Understanding tv Variants\n\nTo add prefixes, we need to analyze the data structure that tv accepts.\n\n#### Regular Variants\n\n```ts\n import { tv } from 'tailwind-variants';\n\n tv({\n variants: {\n foo: {\n foo_val: 'px-2', // or ['pxx-2', ...], be the same, class / className\n },\n }\n })({ foo: 'foo_val' })\n```\n\n#### Boolean Variants (Including true/false keys)\n\n```ts\n tv({\n variants: {\n foo: {\n true: 'px-2',\n false: 'py-2',\n }\n }\n })({ foo: true, })\n```\n\n#### Compound Variants (Intersection between variants)\n\n```ts\n tv({\n variants: {\n foo: {\n foo_val: 'px-2',\n foo_val2: 'px-2',\n },\n bar: {\n true: 'px-2',\n false: 'py-2',\n },\n },\n compoundVariants: [\n {\n foo: 'foo_val', // or ['foo_val', 'foo_val2', ]\n bar: true,\n class: 'text-white', // You can also use \"className\" as the key\n }\n ],\n })({ foo: true, })\n```\n\n#### Responsive Variants (Device screen sizes)\n\n```ts\n tv({\n variants: {\n foo: {\n foo_val: 'px-2',\n foo_val2: 'px-4',\n },\n }\n },\n {\n responsiveVariants: ['sm', 'md'] // or `true` for all\n })({ \n foo: {\n initial: 'foo_val',\n sm: 'foo_val',\n md: 'foo_val2',\n }\n })\n```\n\n#### Slot Variants (Combining above variants with slots)\n\n```ts\n tv({\n slots: {\n slot_a: 'mx-2',\n slot_b: 'mx-2',\n },\n compoundSlots: [\n {\n slots: ['slot_a', 'slot_b', ], \n class: '',\n foo: 'foo_val', // for all slot while variant is missing\n },\n ],\n variants: {\n foo: {\n foo_val: {\n slot_a: 'px-2',\n }\n },\n bar: {\n true: {\n slot_a: 'mx-2'\n },\n false: {\n slot_a: 'mx-0'\n },\n },\n },\n compoundVariants: [\n {\n foo: 'foo_val',\n bar: true,\n class: {\n slot_a: '',\n }\n }\n ],\n {\n responsiveVariants: ['sm', 'md'] // or `true` for all\n }\n })({ \n foo: {\n initial: 'foo_val',\n sm: 'foo_val',\n md: 'foo_val2',\n }\n }) // --> { foo_slot, bar_slot, }\n```\n\n### Summary\n\nAfter adding prefix functionality locally (#3009 ) and configuring tw prefix (while installing uno to handle non-prefix classes in the playground for page styling), **practical usage revealed some unavoidable conflicts, such as at-rule usage. Additionally, this approach doesn't effectively prevent files from being processed twice (by both tw & uno)**. Therefore, let's try a different approach: remove tw completely and use UnoCSS for everything!\n\n\u003C/details>\n\n## Modifying ui\n\n### Disabling tw Plugin\n\nRemove `@tailwindcss/vite` installation handling from ui internals.\nRemove tw imports and specific configurations from ui playground.\n\n### Introducing uno\n\nFor [nuxt](https://unocss.dev/integrations/nuxt) | [vite](https://unocss.dev/integrations/vite)\n\nAlso, [Style Reset](https://unocss.dev/guide/style-reset) can be applied as needed.\n\n**IMPORTANT: Include @nuxt/ui files**\n\n```ts\nexport default defineConfig({\n presets: [\n presetUno(),\n ],\n content: {\n pipeline: {\n include: [\n // the default\n /\\.(vue|svelte|[jt]sx|mdx?|astro|elm|php|phtml|html)($|\\?)/,\n // IMPORTANT include @nuxt/ui files\n /\\.nuxt\\/ui\\//,\n ]\n }\n }\n})\n```\n\n## Primitive Variables\n\nuno doesn't generate primitive variables like tw does (e.g., `--color-green-500`, `--text-lg`, `--radius-md`, etc.), but ui internally needs these variables.\n\n**For now, we'll directly copy the primitive variables from tw's normal loaded to local.**\n\n## Rule Inconsistencies\n\n**There are must more undiscovered issues**\n\n### Ring\n\nIn uno, the default `ring` width is 3px, different from tw's 1px.\n\n**Solution:**\n\n```ts\n shortcuts: {\n ring: 'ring-1'\n },\n```\n\n### Color Opacity\n\ntw internally uses [color-mix](https://developer.mozilla.org/zh-CN/docs/Web/CSS/color_value/color-mix), allowing direct opacity settings for color variables.\nCurrently, uno doesn't support this directly.\n\ntw: `class=\"bg-[var(--color-primary)]/20\"` ✓\nuno: `class=\"bg-[var(--color-primary)]/20\"` ✕\nuno: `class=\"bg-[rgb(255,5,5)]/20\"` ✓\n\n```css\n:root {\n --color-primary: rgb(255, 5, 5);\n}\n```\n\nAfter observing ui usage, uno rules were added:\n\nuno: `class=\"bg-[var(--ui-primaey)]/20\"` ✓\nuno: `class=\"hover:bg-[var(--ui-primaey)]/75\"` ✓\n\n**Solution:**\n\n```ts\n rules: [\n [/(?:([^:\\s]+):)?bg-.*?\\[(var\\(--[^-]+-[^)]+\\))\\]\\/(\\d+)/, function* ([, modifier, color, alpha], { symbols }) {\n yield {\n background: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n if (modifier) {\n yield {\n [symbols.selector]: selector => `${selector}:${modifier}`,\n background: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n }\n }],\n [/(?:([^:\\s]+):)?text-.*?\\[(var\\(--[^-]+-[^)]+\\))\\]\\/(\\d+)/, function* ([, modifier, color, alpha], { symbols }) {\n yield {\n color: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n if (modifier) {\n yield {\n [symbols.selector]: selector => `${selector}:${modifier}`,\n color: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n }\n }]\n ],\n```\n\n---\n\nNow, let's run the playground! ~\n\n## Notes\n\n### tm's handling of tw and uno exclusive rules yields unexpected results\n\ntw doesn't directly support units (px, em, ...) like `text-Xpx`, requiring `text-[Xpx]` instead.\n\n- `text-md text-[20px]` --> `text-[20px]`\n- `text-md text-20px` --> `text-md text-20px`\n- `text-16px text-20px` --> `text-20px`\n- `text-[16px] text-[20px]` --> `text-[20px]`\n\n**When using ui, it's recommended to pass classes that tw can also parse.**\n\n[Commits · byronogis/ui](https://github.com/byronogis/ui/commits/test/use-unocss/)\n\n---\n\n\n[nuxt-ui-href]: https://ui3.nuxt.dev\n[tailwindcss-href]: https://tailwindcss.com/docs/v4-beta\n[tailwind-variants-href]: https://www.tailwind-variants.org/\n[tailwind-merge-href]: https://github.com/dcastil/tailwind-merge\n[unocss-href]: https://unocss.dev/\n[tw-prefix-href]: https://tailwindcss.com/docs/v4-beta#using-a-prefix\n",[3209],{"name":3210,"color":3211},"question","d876e3",3011,"[Attempt] Exploring the Coexistence of Nuxt UI v3 and UnoCSS","2025-05-10T19:47:10Z","https://github.com/nuxt/ui/issues/3011",0.7469488,{"description":3218,"labels":3219,"number":3227,"owner":3147,"repository":3148,"state":3187,"title":3228,"updated_at":3229,"url":3230,"score":3231},"I currently have the problem that we have to integrate our SPA into a larger application. And with that, we also inherit the CSS of the outer application. And that's where it gets really ugly: they have partially written classes in their own CSS files that use the TW naming scheme (m, p, gap, shadow, etc.), and then add `!important` to these declarations. \n\nOne of the big problems with Nuxt UI is that there is no prefixing of Tailwind classes. So we started writing TW utilities with a prefix for the affected classes. This is then transferred to app.config. The second problem was the merge process that app.config uses. Usually the names have to match. If I want to have a `p-4` from the config (because px values with !important were entered in the outer CSS), I created the class `p-00`, which replaces the `p-4` class and thus clears the way for the prefixed TW class `o-p-4`.\n\nSo far so good, but I can't use it with popovers like SelectMenu. No matter what I do, the class `shadow-lg` remains. The other devs of the main application have entered a rather ugly shadow with important there. \n\nIs there another prop like 'content' that I can use to replace `shadow-lg`? I'm not a fan of `!important`, but at this point I can only work this way.\n\nFurthermore, it would be really nice if you could really overwrite the sections in app.config instead of just merging them (apart from prefixing the TW classes). There are certain stylings that you won't use, but then they are in the element",[3220,3221,3222,3225],{"name":3210,"color":3211},{"name":3141,"color":3142},{"name":3223,"color":3224},"closed-by-bot","ededed",{"name":3226,"color":3224},"stale",3874,"Changing Shadow Classes on Popover and SelectMenu","2025-08-12T02:12:50Z","https://github.com/nuxt/ui/issues/3874",0.7537447,{"description":3233,"labels":3234,"number":3237,"owner":3147,"repository":3147,"state":3187,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Environment\n\nNuxt Version: 3.0.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-hcvfnh?file=components/MainHeader.vue\n\n### Describe the bug\n\ni want to overwrite \u003CNuxtLayout name=\"header\" /> style, but it is no work\r\n\r\n``` \r\n\u003Ctemplate>\r\n \u003CNuxtLayout name=\"header\" />\r\n\u003C/template>\r\n\r\n\u003Cstyle lang=\"scss\" scoped>\r\n.header {\r\n color: black;\r\n}\r\n\u003C/style>\r\n``` \r\n\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3235,3236],{"name":3196,"color":3197},{"name":3199,"color":3200},15572,"overwrite layout component style no work ","2023-01-24T14:02:38Z","https://github.com/nuxt/nuxt/issues/15572",0.7559397,{"description":3243,"labels":3244,"number":3252,"owner":3147,"repository":3148,"state":3187,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.17.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@8.12.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\nnuxt/ui-pro 1.4.3\n\n### Reproduction\n\n```ts\n// package.json\n\"@nuxt/ui-pro\": \"^1.4.3\",\n\"nuxt\": \"^3.13.2\",\n```\n\n\n### Description\n\nThe property `class` in a link object seems not to be used by `UHeaderLinks` or cannot override UI config from prop or the app.config.ts file.\n\nProperty `icon` is not used on the parent object but appears for children.\n\n\n\n```vue\n\u003Cscript setup lang=\"ts\">\n const links = [\n {\n label: 'Foo',\n to: '/foo',\n icon: 'i-mdi-car',\n },\n {\n label: 'Bar',\n to: '/bar',\n icon: 'i-mdi-star',\n class: 'text-red-500 italic',\n },\n {\n label: 'Baz',\n children: [\n {\n label: 'Baz Foo',\n to: '/foo',\n icon: 'i-mdi-car',\n class: 'text-red-500 italic',\n },\n {\n label: 'Baz Bar',\n to: '/bar',\n icon: 'i-mdi-star',\n class: 'text-red-500 italic',\n },\n ],\n },\n ]\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUHeader>\n \u003Ctemplate #logo> ... \u003C/template>\n \u003Ctemplate #center>\n \u003CUHeaderLinks\n :links=\"links\"\n :ui=\"{\n wrapper: 'hidden lg:flex flex-row flex-nowrap items-center gap-x-8',\n }\"\n />\n \u003C/template>\n\n \u003Ctemplate #panel>\n \u003Cdiv class=\"flex h-full content-center pt-[130px]\">\n \u003CUNavigationTree id=\"navtree\" :links=\"links\" default-open />\n \u003C/div>\n \u003C/template>\n \u003C/UHeader>\n\u003C/template>\n```\n\n### Workaround \nFor classes: split links in multiple UHeaderLinks with custom ui prop.\n\n\n\n```vue\n\u003Ctemplate #center>\n \u003Cdiv class=\"flex flex-row flex-nowrap gap-5\">\n \u003CUHeaderLinks\n :links=\"linksA\"\n :ui=\"{\n wrapper: 'hidden lg:flex flex-row flex-nowrap items-center gap-x-8',\n }\"\n />\n \u003CUHeaderLinks\n :links=\"linksB\"\n :ui=\"{\n wrapper: 'hidden lg:flex flex-row flex-nowrap items-center gap-x-8',\n inactive: 'hover:text-primary text-red-500 italic',\n default: {\n popover: {\n ui: {\n wrapper: 'text-red-500 italic',\n },\n },\n },\n }\"\n />\n \u003C/div>\n\u003C/template>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3245,3246,3249,3250,3251],{"name":3158,"color":3159},{"name":3247,"color":3248},"nuxt/ui-pro","00dc82",{"name":3144,"color":3145},{"name":3223,"color":3224},{"name":3226,"color":3224},2306,"HeaderLinks: properties class and icon has no effects","2025-06-18T09:06:02Z","https://github.com/nuxt/ui/issues/2306",0.75895107,{"description":3258,"labels":3259,"number":3263,"owner":3147,"repository":3147,"state":3187,"title":3264,"updated_at":3265,"url":3266,"score":3267},"# **Problem** \r\nUsing `\u003Cstyle module>` in Vue single-page component to implement CSS Modules, duplicate style declarations are being injected into `\u003Chead>` but only when accessing the page directly. When accessed via router (i.e. from another page via a `\u003Cnuxt-link>`), the behaviour seems to be as expected. The number of times it's injected corresponds to the number of components in which one of its classes are 'composed'. \r\n\r\n\r\n## **Page accessed directly** \r\n\r\n\r\n\r\n\r\n## **Page accessed via `\u003Cnuxt-link>`** \r\n\r\n\r\n\r\n\r\n## **Example component (ui-a.vue)** \r\n```html\r\n\u003Ctemplate>\r\n \u003Csection :class=\"$style.root\">\u003C/section>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nexport default {}\r\n\u003C/script>\r\n\r\n\u003Cstyle lang=\"scss\" module>\r\n\r\n/* Dependencies\r\n========================================================================== */\r\n@value c-background-color \"sass-loader!~/assets/styles/cosmetics/cosmetics.background-color.scss\"; \r\n\r\n\r\n/* Root class\r\n========================================================================== */\r\n.root {\r\n composes: purple from c-background-color;\r\n padding: 20px;\r\n}\r\n\r\n\u003C/style>\r\n``` \r\n\r\n\r\n## **Build.extend modifications** \r\n```javascript\r\nbuild: {\r\n extend (config, ctx) {\r\n const vueLoader = config.module.rules.find(({loader}) => loader === 'vue-loader')\r\n vueLoader.options.cssModules = {\r\n localIdentName: '[name]__[local]'\r\n }\r\n ...\r\n }\r\n ...\r\n}\r\n``` \r\n\r\n\r\n## **Expected** \r\nI'm a noob with absolutely all of this stuff (CSS Modules and SSR in particular), but I'd expect it to behave as it does in the second screenshot. No matter how many classes `compose` `.class-X`, `class-X`'s stylesheet should only be injected once.\r\n\r\n\r\n## **Additional Info** \r\nI've tried to keep the demo repo as minimal as I can. I've also published the static site to gh-pages:\r\nREPO: https://github.com/thisguyscode/nuxt-styleguide/tree/demo\r\nSTATIC: https://thisguyscode.github.io/nuxt-styleguide/ \r\n\r\nReally I'm new to all of this - just a designer trying to play with all you smart peoples' shiny new toys. If anyone has even a little insight it would be a great help. I've looked through issues on other related repos, and the only promising one was https://github.com/css-modules/css-modules/issues/180, but that turned out not to help. \r\n\r\nP.S. MAD love for the Nuxt team on all their hard work. Even a dunce like me was able to throw together a [portfolio site that doesn't suck with Nuxt](https://tinyworld.xyz). Complete overkill for the purpose of course but a lot of learning and fun was involved so thanks Nuxt!!! \r\n\r\n\r\n\r\n\r\n\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1900\">#c1900\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3260],{"name":3261,"color":3262},"2.x","d4c5f9",2143,"CSS Modules: Redudant styles injected to \u003Chead> when accessing page directly","2023-01-18T15:43:10Z","https://github.com/nuxt/nuxt/issues/2143",0.75918907,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjje3mLl50_iNS-zy8aMYycMOgCxX9CBpNjC8pGQfUjk":-1},"/nuxt/ui/4953"]