\r\n\u003C/Suspense>\r\n```\r\nthen data fetching within that component gets repeated on the client after page load even though component is already server rendered.\r\n\r\n\r\nIf we remove `Suspense` or use string literal in `resolveComponent` everything works fine.\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2973,2974],{"name":2957,"color":2958},{"name":2960,"color":2961},26101,"Double fetching when using dynamic components with resolveComponent and Suspense","2024-03-06T13:48:41Z","https://github.com/nuxt/nuxt/issues/26101",0.6600007,{"description":2981,"labels":2982,"number":2985,"owner":2947,"repository":2947,"state":2965,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\nbut also Windows\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-uvnsdy?file=app.vue,components%2FLazy.vue,layouts%2Fdefault.vue,pages%2Findex.vue,components%2FLoader.vue\r\n\r\n### Describe the bug\r\n\r\nIn the reproduction repo there are two buttons which trigger dynamic (lazy) load of components. I would assume that both of the solutions would correctly trigger one of loading states (either `fallback` slot in `Suspense` component or `loadingComponent` when using `defineAsyncComponent`). Meanwhile it does not trigger any of it and only ocasionally shows them up during hot reload. I am not sure if this is a bug or correct behavior.\r\n\r\nThe thing is I would like some kind of global overlay with loading status to show up during waiting for some modal or side panel gets loaded (quite standard thing, I think). So the issue is that when I simulate slow network or just use this timeouts to simulate long load of component I cannot get this to work correctly. For reference this is example Vue project which properly loads the component with loader status:\r\nhttps://stackblitz.com/edit/vue3-vite-typescript-starter-hn8dyy?file=src%2Fcomponents%2FHelloWorld.vue,src%2FApp.vue\r\n\r\n### Additional context\r\nI found this issue https://github.com/nuxt/nuxt/issues/15648, but I don't quite understand why the provided repo does not work correctly anyway. I get it that `NuxtPage` component wraps all the content inside `\u003CSuspense>` tag, but there is also an \"outer\" suspense in `app.vue` which should work. Also I'd assume that since the `\u003CSuspense>` wraps `\u003CNuxtPage>` content I could just do something like\r\n\r\n```\r\n\u003Ctemplate>\r\n\u003CNuxtPage>\r\n\u003CNuxtLoadingIndicator />\r\n\r\n\u003CLazySomeComponent v-if=\"displayComponent\" />\r\n\u003C/NuxtPage>\r\n```\r\nand then `NuxtLoadingIndicator` would \"catch\" load of async component (since it is in Suspense context) and display this indicator on the page (which also does not happen).\r\n### Logs\r\n\r\n_No response_",[2983,2984],{"name":2957,"color":2958},{"name":2960,"color":2961},26824,"Dynamic component loader not showing up","2024-04-17T18:35:29Z","https://github.com/nuxt/nuxt/issues/26824",0.66033727,{"labels":2991,"number":2997,"owner":2947,"repository":2947,"state":2965,"title":2998,"updated_at":2999,"url":3000,"score":3001},[2992,2995,2996],{"name":2993,"color":2994},"question","cc317c",{"name":2957,"color":2958},{"name":2960,"color":2961},13320,"suspense.resolve() is called without a pending branch","2023-01-19T16:52:33Z","https://github.com/nuxt/nuxt/issues/13320",0.668701,{"description":3003,"labels":3004,"number":3012,"owner":2947,"repository":2947,"state":2965,"title":3013,"updated_at":3014,"url":3015,"score":3016},"### Version\n\n[v2.9.2](https://github.com/nuxt.js/releases/tag/v2.9.2)\n\n### Reproduction link\n\n[https://github.com/raWINce/nuxt-async-loading-client-side-hydration](https://github.com/raWINce/nuxt-async-loading-client-side-hydration)\n\n### Steps to reproduce\n\n- in a component render html that depends on the viewport (e.g. using [`vue-mq`](https://github.com/AlexandreBonaventure/vue-mq) with `v-if=\"$mq === 'lg'\"`)\n- include those components as an [async component](https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components)\n- reload the page on a different viewport\n\n### What is expected ?\n\nDo not throw warning/errors after reloading the page (during client hydration).\n\nThe client hydration should work with async components, too, when using e.g. [nuxt-mq](https://www.npmjs.com/package/nuxt-mq)-dependent html.\n\n### What is actually happening?\n\nAfter reloading, the client hydration fails and throws `[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside \u003Cp>, or missing \u003Ctbody>. Bailing hydration and performing full client-side render.`.\n\nIn a more complicated setup this leads to an error that crashes the entire app (i.e. all components that are rendered later in the DOM do not work). I did not have time to make an example for this case, though\n\n### Additional comments?\n\n- Wrapping the component within `no-ssr` solves the issue. This, however, is not a solution for me because I need the html to be rendered on the server, which is the reason for choosing nuxt in the first place\n- including the component without dynamic import also solves the issue. \n - this makes me think that viewport dependent html can work with nuxt\n - hence, this is probably not a `nuxt-mq` issue\n\n\n\n\n\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9765\">#c9765\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3005,3008,3009],{"name":3006,"color":3007},"stale","ffffff",{"name":2960,"color":2961},{"name":3010,"color":3011},"2.x","d4c5f9",6403,"Client hydration fails with async components and breakpoint dependent html","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6403",0.67100155,{"labels":3018,"number":3021,"owner":2947,"repository":2947,"state":2965,"title":3022,"updated_at":3023,"url":3024,"score":3025},[3019,3020],{"name":2957,"color":2958},{"name":2960,"color":2961},13745,"useAsyncData causes hydration issues","2023-01-19T17:04:40Z","https://github.com/nuxt/nuxt/issues/13745",0.67284936,{"labels":3027,"number":3030,"owner":2947,"repository":2947,"state":2965,"title":3031,"updated_at":3032,"url":3033,"score":3034},[3028,3029],{"name":2957,"color":2958},{"name":2960,"color":2961},22653,"Hydration node mismatch - but client and server is the same","2023-08-16T14:45:59Z","https://github.com/nuxt/nuxt/issues/22653",0.679082,{"description":3036,"labels":3037,"number":3042,"owner":2947,"repository":2947,"state":2965,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-qjtrhd-mtyvxv\r\n\r\n### Describe the bug\r\n\r\n```vue\r\n\u003C!-- MyWrapper.server.vue -->\r\n\u003Ctemplate>\r\n \u003CAnotherServerComponent />\r\n\u003C/template>\r\n```\r\n\r\nDirectly using a server component as another server component's root will cause a hydration warning:\r\n```\r\nruntime-core.esm-bundler.js:48 [Vue warn]: Hydration node mismatch:\r\n- rendered on server: \u003C!--]--> \r\n- expected on client: Symbol(v-fgt) \r\n at \u003CNuxtIsland name=\"MyWrapper\" lazy=false props= Proxy(Object) {} ... > \r\n at \u003CMyWrapper> \r\n at \u003CApp key=4 > \r\n at \u003CNuxtRoot>\r\n```\r\n\r\n```\r\n[Vue warn]: Hydration children mismatch on \u003Cdiv data-v-inspector=\"app.vue:4:3\">…\u003C/div> \r\nServer rendered element contains fewer child nodes than client vdom. \r\n at \u003CNuxtIsland name=\"MyWrapper\" lazy=false props= Proxy(Object) {} ... > \r\n at \u003CMyWrapper> \r\n at \u003CApp key=4 > \r\n at \u003CNuxtRoot>\r\n```\r\n\r\nI think it is at least an undocumented behavior.\r\n\r\n### Additional context\r\n\r\nThe previous post in https://github.com/nuxt/nuxt/issues/27731#issuecomment-2180766312 was ignored so I reopened a new issue.\r\n\r\n### Logs\r\n\r\n_No response_",[3038,3041],{"name":3039,"color":3040},"documentation","5319e7",{"name":2944,"color":2945},27810,"Server component cannot be the root element of another server component","2024-07-11T11:56:47Z","https://github.com/nuxt/nuxt/issues/27810",0.6794948,{"description":3048,"labels":3049,"number":3052,"owner":2947,"repository":2947,"state":2965,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Environment\r\n\r\n❯ npx nuxi info\r\nWorking directory: /home/projects/github-423jt1 16:55:22\r\nNuxt project info: 16:55:22\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.0\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-423jt1?file=pages%2Findex.vue\r\n\r\nThis minimal reproduction has: Two pages, one .client.vue component on the home page, and some navigation links to navigate between the two pages.\r\n\r\nSteps:\r\n1. See that when the home page loads 'A Component' is displayed\r\n2. Navigate to another Page\r\n3. Navigate back to Home\r\n4. See that the component is not displayed\r\n5. Check developer tools for some error messages (shown in the 'Logs' section below)\r\n\r\n### Describe the bug\r\n\r\nOn the homepage there is a client only component (marked with the .client.vue suffix)\r\nThis component displays on page load, but if you navigate to another page and navigate back again, it has disappeared. There are some error messages in the developer tools (copied below)\r\n\r\n### Additional context\r\n\r\nI want to mark relevant components as client only so that they don't get compiled into the server bundle in order reduce bundle size.\r\n\r\n### Logs\r\n\r\n\r\nIn the developer tools we get an error message saying the following:\r\n\r\n```shell-script\r\nchunk-UJJZ7LWV.js:1436 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core \r\n at \u003CAComponent.client> \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C Proxy(Object) {…} > > \r\n at \u003CRouteProvider key=\"/\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/', path: '/', query: {…}, hash: '', name: 'index', …} ... > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\nwarn2 @ chunk-UJJZ7LWV.js:1436\r\nlogError @ chunk-UJJZ7LWV.js:1610\r\nhandleError @ chunk-UJJZ7LWV.js:1602\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1554\r\nflushJobs @ chunk-UJJZ7LWV.js:1755\r\nflushJobs @ chunk-UJJZ7LWV.js:1765\r\nPromise.then (async)\r\nqueueFlush @ chunk-UJJZ7LWV.js:1668\r\nqueuePostFlushCb @ chunk-UJJZ7LWV.js:1688\r\nqueueEffectWithSuspense @ chunk-UJJZ7LWV.js:3004\r\nscheduler @ chunk-UJJZ7LWV.js:3171\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:603\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\nset value @ chunk-UJJZ7LWV.js:1246\r\ndoSet @ chunk-UJJZ7LWV.js:5865\r\nsetRef @ chunk-UJJZ7LWV.js:5876\r\n(anonymous) @ chunk-UJJZ7LWV.js:5797\r\nsetRef @ chunk-UJJZ7LWV.js:5796\r\nunmount @ chunk-UJJZ7LWV.js:7611\r\nunmountComponent @ chunk-UJJZ7LWV.js:7723\r\nunmount @ chunk-UJJZ7LWV.js:7624\r\nresolve @ chunk-UJJZ7LWV.js:2780\r\n(anonymous) @ chunk-UJJZ7LWV.js:2906\r\nPromise.then (async)\r\nregisterDep @ chunk-UJJZ7LWV.js:2870\r\nmountComponent @ chunk-UJJZ7LWV.js:7034\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\nmountChildren @ chunk-UJJZ7LWV.js:6711\r\nmountElement @ chunk-UJJZ7LWV.js:6618\r\nprocessElement @ chunk-UJJZ7LWV.js:6583\r\npatch @ chunk-UJJZ7LWV.js:6455\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7137\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\nsetupRenderEffect @ chunk-UJJZ7LWV.js:7251\r\nmountComponent @ chunk-UJJZ7LWV.js:7041\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7137\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\nsetupRenderEffect @ chunk-UJJZ7LWV.js:7251\r\nmountComponent @ chunk-UJJZ7LWV.js:7041\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\npatchSuspense @ chunk-UJJZ7LWV.js:2670\r\nprocess @ chunk-UJJZ7LWV.js:2473\r\npatch @ chunk-UJJZ7LWV.js:6492\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7202\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1552\r\nflushJobs @ chunk-UJJZ7LWV.js:1755\r\nPromise.then (async)\r\nqueueFlush @ chunk-UJJZ7LWV.js:1668\r\nqueueJob @ chunk-UJJZ7LWV.js:1662\r\n(anonymous) @ chunk-UJJZ7LWV.js:7239\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:603\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\nset value @ chunk-UJJZ7LWV.js:1246\r\nfinalizeNavigation @ vue-router.js:2563\r\n(anonymous) @ vue-router.js:2473\r\nPromise.then (async)\r\npushWithRedirect @ vue-router.js:2441\r\npush @ vue-router.js:2367\r\nnavigate @ vue-router.js:1621\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1552\r\ncallWithAsyncErrorHandling @ chunk-UJJZ7LWV.js:1560\r\ninvoker @ chunk-UJJZ7LWV.js:9752\r\n```\r\n\r\nand \r\n\r\n```\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-UJJZ7LWV.js:9197:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-UJJZ7LWV.js:7206:11)\r\n at ReactiveEffect.run (chunk-UJJZ7LWV.js:422:19)\r\n at instance.update (chunk-UJJZ7LWV.js:7243:52)\r\n at callWithErrorHandling (chunk-UJJZ7LWV.js:1552:32)\r\n at flushJobs (chunk-UJJZ7LWV.js:1755:9)\r\n at flushJobs (chunk-UJJZ7LWV.js:1765:7)\r\nparentNode @ chunk-UJJZ7LWV.js:9197\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7206\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1552\r\nflushJobs @ chunk-UJJZ7LWV.js:1755\r\nflushJobs @ chunk-UJJZ7LWV.js:1765\r\nPromise.then (async)\r\nnextTick @ chunk-UJJZ7LWV.js:1635\r\nonResolve @ page.js?v=2b17d26d:81\r\ntriggerEvent @ chunk-UJJZ7LWV.js:2494\r\nresolve @ chunk-UJJZ7LWV.js:2811\r\n(anonymous) @ chunk-UJJZ7LWV.js:2906\r\nPromise.then (async)\r\nregisterDep @ chunk-UJJZ7LWV.js:2870\r\nmountComponent @ chunk-UJJZ7LWV.js:7034\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\nmountChildren @ chunk-UJJZ7LWV.js:6711\r\nmountElement @ chunk-UJJZ7LWV.js:6618\r\nprocessElement @ chunk-UJJZ7LWV.js:6583\r\npatch @ chunk-UJJZ7LWV.js:6455\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7137\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\nsetupRenderEffect @ chunk-UJJZ7LWV.js:7251\r\nmountComponent @ chunk-UJJZ7LWV.js:7041\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7137\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\nsetupRenderEffect @ chunk-UJJZ7LWV.js:7251\r\nmountComponent @ chunk-UJJZ7LWV.js:7041\r\nprocessComponent @ chunk-UJJZ7LWV.js:6994\r\npatch @ chunk-UJJZ7LWV.js:6467\r\npatchSuspense @ chunk-UJJZ7LWV.js:2670\r\nprocess @ chunk-UJJZ7LWV.js:2473\r\npatch @ chunk-UJJZ7LWV.js:6492\r\ncomponentUpdateFn @ chunk-UJJZ7LWV.js:7202\r\nrun @ chunk-UJJZ7LWV.js:422\r\ninstance.update @ chunk-UJJZ7LWV.js:7243\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1552\r\nflushJobs @ chunk-UJJZ7LWV.js:1755\r\nPromise.then (async)\r\nqueueFlush @ chunk-UJJZ7LWV.js:1668\r\nqueueJob @ chunk-UJJZ7LWV.js:1662\r\n(anonymous) @ chunk-UJJZ7LWV.js:7239\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:603\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\n(anonymous) @ chunk-UJJZ7LWV.js:1358\r\ntriggerEffect @ chunk-UJJZ7LWV.js:613\r\ntriggerEffects @ chunk-UJJZ7LWV.js:598\r\ntriggerRefValue @ chunk-UJJZ7LWV.js:1202\r\nset value @ chunk-UJJZ7LWV.js:1246\r\nfinalizeNavigation @ vue-router.js:2563\r\n(anonymous) @ vue-router.js:2473\r\nPromise.then (async)\r\npushWithRedirect @ vue-router.js:2441\r\npush @ vue-router.js:2367\r\nnavigate @ vue-router.js:1621\r\ncallWithErrorHandling @ chunk-UJJZ7LWV.js:1552\r\ncallWithAsyncErrorHandling @ chunk-UJJZ7LWV.js:1560\r\ninvoker @ chunk-UJJZ7LWV.js:9752\r\n```\r\n```\r\n",[3050,3051],{"name":2957,"color":2958},{"name":2960,"color":2961},23939,".client.vue components causing bug on page navigation","2023-10-30T15:09:54Z","https://github.com/nuxt/nuxt/issues/23939",0.67967874,["Reactive",3058],{},["Set"],["ShallowReactive",3061],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fOlSkKxLWtt7w-Z_ju1HrfP0d4TMvSivpU8AFmGiJj6c":-1},"/nuxt/nuxt/25317"]