\n \u003C/div>\n \u003C/u-button>\n \u003C/template>\n\n \u003Ctemplate #item=\"{ item }\">\n // Content\n \u003C/template>\n\u003C/u-accordion>\n```\n\nCurrently i don't see a way with the default slot to override the AccordionRoot trigger\n",[2867,2870],{"name":2868,"color":2869},"question","d876e3",{"name":2871,"color":2872},"v3","49DCB8",3455,"nuxt","ui","open","Override Slot for Accordion Trigger","2025-03-04T17:30:46Z","https://github.com/nuxt/ui/issues/3455",0.7492154,{"description":2882,"labels":2883,"number":2884,"owner":2874,"repository":2885,"state":2876,"title":2886,"updated_at":2887,"url":2888,"score":2889},"I'm assuming it's the line heights overlapping but I'm not really sure. But you have to be very careful to copy a single line \r\n\r\nhttps://github.com/user-attachments/assets/ccc23fea-e891-446a-ab64-380cafd9dde4",[],1660,"nuxt.com","Bug: Jittery highlight/selection of code","2024-12-04T08:54:36Z","https://github.com/nuxt/nuxt.com/issues/1660",0.76206774,{"description":2891,"labels":2892,"number":2900,"owner":2874,"repository":2875,"state":2876,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Environment\n\nsandbox\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/admiring-herschel-qyt4kh\n\n### Description\n\n`app.config`\n\n```\nbutton: {\n compoundVariants: [\n {\n color: 'primary',\n variant: 'soft',\n class: {\n base: 'text-green-500',\n leadingIcon: 'text-red-500'\n }\n },\n ]\n}\n```\n\nif button defined like without `active` the icon is red, but text is green\n```\n\u003CUButton\n label=\"Label\"\n color=\"primary\"\n variant=\"soft\"\n icon=\"mdi-account\"\n />\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[2893,2896,2897],{"name":2894,"color":2895},"bug","d73a4a",{"name":2871,"color":2872},{"name":2898,"color":2899},"triage","ffffff",3972,"Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.7918844,{"description":2906,"labels":2907,"number":2909,"owner":2874,"repository":2910,"state":2876,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[2908],{"name":2894,"color":2895},684,"test-utils","mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.7919704,{"description":2916,"labels":2917,"number":2921,"owner":2874,"repository":2875,"state":2922,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, components, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0, @pinia/nuxt@0.10.1, compodium@0.1.0-beta.5\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUInputMenu :items=\"idList\" v-model=\"value\" />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(0)\nconst idList = ref([168, 170, 203])\n\u003C/script>\n```\n\n### Description\n\nIf adding array of numbers to InputMenu the menu isn't closing after choosing a number.\nOnly way to close it is double-clicking on the dropdown arrow.\nThe Console shows an error in useFilter.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: string.normalize is not a function\n at contains (useFilter.js?v=87101672:23:21)\n at InputMenu.vue:114:18\n at wrappedFn (reactivity.esm-bundler.js?v=87101672:820:19)\n at Array.filter (\u003Canonymous>)\n at apply (reactivity.esm-bundler.js?v=87101672:828:27)\n at Proxy.filter (reactivity.esm-bundler.js?v=87101672:720:12)\n at InputMenu.vue:112:50\n at Array.map (\u003Canonymous>)\n at ComputedRefImpl.fn (InputMenu.vue:112:27)\n at refreshComputed (reactivity.esm-bundler.js?v=87101672:353:29)\n```",[2918,2919,2920],{"name":2894,"color":2895},{"name":2871,"color":2872},{"name":2898,"color":2899},3606,"closed","Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.7708545,{"description":2928,"labels":2929,"number":2933,"owner":2874,"repository":2910,"state":2922,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v18.19.0\n- Nuxt Version: 3.12.4\n- CLI Version: 3.13.2\n- Nitro Version: 2.9.7\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\nhttps://stackblitz.com/~/github.com/inouetakuya/nuxt-test-utils-playground/pull/3\n\nGitHub: https://github.com/inouetakuya/nuxt-test-utils-playground/pull/3\n\n### Describe the bug\n\nHere is the page component using the Options API.\n\n```vue\n\u003Cscript lang=\"ts\"> \nexport default defineNuxtComponent({ \n name: 'OptionsApiPage', \n setup() { \n return { \n greetingInSetup: 'Hello, setup!', \n }; \n }, \n async asyncData() { \n return { \n greetingInAsyncData: 'Hello, asyncData!', \n }; \n }, \n data() { \n return { \n greetingInData: 'Hello, data!', \n }; \n }, \n computed: { \n greetingInComputed() { \n return 'Hello, computed property!'; \n }, \n }, \n}); \n\u003C/script> \n \n\u003Ctemplate> \n \u003Cp data-testid=\"greeting-in-setup\">greetingInSetup: {{ greetingInSetup }}\u003C/p> \n \u003Cp data-testid=\"greeting-in-async-data\"> \n greetingInAsyncData: {{ greetingInAsyncData }} \n \u003C/p> \n \u003Cp data-testid=\"greeting-in-data\">greetingInData: {{ greetingInData }}\u003C/p> \n \u003Cp data-testid=\"greeting-in-computed\"> \n greetingInComputed: {{ greetingInComputed }} \n \u003C/p> \n\u003C/template>\n```\n\nWhen testing this page component using the mountSuspended method, the data and computed properties of the Options API are not rendered. \n\nOn the other hand, if the same page component is tested with the mount method, both the Options API data and the computed properties are rendered.\n\n```ts\nimport { mountSuspended } from '@nuxt/test-utils/runtime'; \nimport { mount, flushPromises } from '@vue/test-utils'; \nimport OptionsApiPage from '~/pages/options-api.vue'; \n \ndescribe('OptionsApiPage', () => { \n let wrapper; \n \n describe('Using mountSuspended', () => { \n beforeEach(async () => { \n wrapper = await mountSuspended(OptionsApiPage, { \n route: '/options-api', \n }); \n }); \n \n it('should render greeting in setup', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-setup\"]').text()).toBe( \n 'greetingInSetup: Hello, setup!', \n ); \n }); \n \n it('should render greeting in asyncData', () => { \n expect( \n wrapper.find('[data-testid=\"greeting-in-async-data\"]').text(), \n ).toBe('greetingInAsyncData: Hello, asyncData!'); \n }); \n \n it('should render greeting in data', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe( \n 'greetingInData: Hello, data!', \n ); \n }); \n \n it('should render greeting in computed', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe( \n 'greetingInComputed: Hello, computed property!', \n ); \n }); \n }); \n \n describe('Using mount', () => { \n beforeEach(async () => { \n const component = defineComponent({ \n components: { OptionsApiPage }, \n template: '\u003CSuspense>\u003COptionsApiPage />\u003C/Suspense>', \n }); \n wrapper = mount(component); \n await flushPromises(); \n }); \n \n it('should render greeting in setup', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-setup\"]').text()).toBe( \n 'greetingInSetup: Hello, setup!', \n ); \n }); \n \n it('should render greeting in asyncData', () => { \n expect( \n wrapper.find('[data-testid=\"greeting-in-async-data\"]').text(), \n ).toBe('greetingInAsyncData: Hello, asyncData!'); \n }); \n \n it('should render greeting in data', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe( \n 'greetingInData: Hello, data!', \n ); \n }); \n \n it('should render greeting in computed', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe( \n 'greetingInComputed: Hello, computed property!', \n ); \n }); \n }); \n});\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n$ npm test\n\n> test\n> vitest run\n\n\n RUN v2.0.5 /Users/inouetakuya/src/github.com/inouetakuya/nuxt-test-utils-playground\n\nstdout | pages/script-setup.nuxt.spec.ts\n\u003CSuspense> is an experimental feature and its API will likely change.\n\nstdout | pages/options-api.nuxt.spec.ts\n\u003CSuspense> is an experimental feature and its API will likely change.\n\n ❯ pages/options-api.nuxt.spec.ts (8)\n ❯ OptionsApiPage (8)\n ❯ Using mountSuspended (4)\n ✓ should render greeting in setup\n ✓ should render greeting in asyncData\n × should render greeting in data\n × should render greeting in computed\n ✓ Using mount (4)\n ✓ pages/script-setup.nuxt.spec.ts (1)\n ✓ utils/example-util.spec.ts (1)\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL pages/options-api.nuxt.spec.ts > OptionsApiPage > Using mountSuspended > should render greeting in data\nAssertionError: expected 'greetingInData:' to be 'greetingInData: Hello, data!' // Object.is equality\n\nExpected: \"greetingInData: Hello, data!\"\nReceived: \"greetingInData:\"\n\n ❯ pages/options-api.nuxt.spec.ts:28:71\n 26|\n 27| it('should render greeting in data', () => {\n 28| expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe(\n | ^\n 29| 'greetingInData: Hello, data!',\n 30| );\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯\n\n FAIL pages/options-api.nuxt.spec.ts > OptionsApiPage > Using mountSuspended > should render greeting in computed\nAssertionError: expected 'greetingInComputed:' to be 'greetingInComputed: Hello, computed p…' // Object.is equality\n\nExpected: \"greetingInComputed: Hello, computed property!\"\nReceived: \"greetingInComputed:\"\n\n ❯ pages/options-api.nuxt.spec.ts:34:75\n 32|\n 33| it('should render greeting in computed', () => {\n 34| expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe(\n | ^\n 35| 'greetingInComputed: Hello, computed property!',\n 36| );\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯\n\n Test Files 1 failed | 2 passed (3)\n Tests 2 failed | 8 passed (10)\n Start at 16:38:07\n Duration 740ms (transform 303ms, setup 513ms, collect 188ms, tests 41ms, environment 237ms, prepare 331ms)\n```\n",[2930],{"name":2931,"color":2932},"pending triage","5D08F5",961,"mountSuspended does not render Options API's data and computed properties","2024-10-08T13:30:47Z","https://github.com/nuxt/test-utils/issues/961",0.7714227,{"description":2939,"labels":2940,"number":2941,"owner":2874,"repository":2910,"state":2922,"title":2942,"updated_at":2943,"url":2944,"score":2945},"When updating from 3.0.0.rc9 to 3.3.1 I see this error:\r\n\r\n```\r\n ERROR TypeError: filters.some is not a function 16:18:54\r\n\r\n ❯ node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:51 16:18:54\r\n ❯ Vitest.globTestFiles node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:29 16:18:54\r\n ❯ process.processTicksAndRejections node:internal/process/task_queues:95:5 16:18:54\r\n ❯ Vitest.start node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10472:50 16:18:54\r\n ❯ startVitest node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:11204:5 16:18:54\r\n ❯ runTests node_modules/@nuxt/test-utils/dist/index.mjs:311:21 16:18:54\r\n ❯ Object.invoke node_modules/nuxi/dist/chunks/test.mjs:14:5 16:18:54\r\n ❯ _main node_modules/nuxi/dist/cli.mjs:49:20 \r\n```",[],305,"TypeError: filters.some is not a function ","2023-12-02T00:23:10Z","https://github.com/nuxt/test-utils/issues/305",0.775738,{"description":2947,"labels":2948,"number":2941,"owner":2874,"repository":2875,"state":2922,"title":2953,"updated_at":2954,"url":2955,"score":2945},"### Additional context\r\nA splitter component that adds fuctionality for resizable \"Pane\" component and optional min and max size props.\r\n\r\nSome examples:\r\nhttps://volta.net/inbox\r\nhttps://ark-ui.com/docs/react/components/splitter\r\n",[2949,2952],{"name":2950,"color":2951},"feature","A27AF6",{"name":2871,"color":2872},"[Splitter] Implement component","2025-04-16T13:18:10Z","https://github.com/nuxt/ui/issues/305",{"description":2957,"labels":2958,"number":2959,"owner":2874,"repository":2960,"state":2922,"title":2961,"updated_at":2962,"url":2963,"score":2964},"Hello,\nadding your package to the a repository for deploying breaks the Rollup build step.\n\n## Minimal reproducible example\n```\nnode --version\nv20.17.0\npnpm --version\n9.11.0\n```\n- `pnpm create cloudflare@latest my-nuxt-app --framework=nuxt`\n- `cd my-nuxt-app`\n- `pnpx nuxi module add icon` (taken from your doc)\n- `pnpm build`\nI get the following error:\n\n```\n[nitro 23:41:30] ERROR RollupError: .nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js (1:9): \"stdin\" is not exported by \"node_modules/.pnpm/unenv@1.10.0/node_modules/unenv/runtime/node/process/index.mjs\", imported by \".nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js\".\n\n\n1: import { stdin, stdout } from \"node:process\";\n ^\n2: import f from \"node:readline\";\n3: import { WriteStream } from \"node:tty\";\n\n\n[23:41:30] ERROR .nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js (1:9): \"stdin\" is not exported by \"node_modules/.pnpm/unenv@1.10.0/node_modules/unenv/runtime/node/process/index.mjs\", imported by \".nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js\".\n```\n\nThanks.",[],274,"icon","Rollup issue - Adding the package breaks the build step","2024-10-28T13:36:54Z","https://github.com/nuxt/icon/issues/274",0.7824217,{"labels":2966,"number":2974,"owner":2874,"repository":2874,"state":2922,"title":2975,"updated_at":2976,"url":2977,"score":2978},[2967,2969,2971],{"name":2968,"color":2899},"stale",{"name":2931,"color":2970},"E99695",{"name":2972,"color":2973},"2.x","d4c5f9",8305,"WatchQuery not working in static deployed site","2023-01-22T15:38:17Z","https://github.com/nuxt/nuxt/issues/8305",0.7884221,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJ2oz4KrAAfJX8C2-5pWkHxFeFtwIrUvXFm0KhKLEGMs":-1},"/nuxt/nuxt.com/1244"]