\r\n \u003Ctemplate v-else-if=\"entry\">\r\n \u003Chero-builder :entry=\"entry\"/>\r\n \u003Cbuilder-landing-page :entry=\"entry\"/>\r\n \u003C/template>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\r\n\u003Cscript setup>\r\n import {entryMeta} from '~/helpers';\r\n import groqQuery from '~/queries/groq/home-page';\r\n const config = useRuntimeConfig();\r\n const route = useRoute();\r\n const query = groqQuery();\r\n\r\n const { pending, data:entry, error } = useSanityQuery(query);\r\n console.log({pending: pending.value, error:error.value, entry:entry.value});\r\n if (error && error.value) {\r\n throw createError({statusCode:500})\r\n } else if (entry) {\r\n const meta = entryMeta(entry.value);\r\n useHead({\r\n title:entry.value?.meta?.title,\r\n meta: meta,\r\n link: [\r\n {rel:'canonical',href:'/'}\r\n ]\r\n })\r\n } else {\r\n console.error('Unknown error occured')\r\n }\r\n\u003C/script>\r\n \r\n```\r\n\r\nand here is my nuxt.config:\r\n\r\n```\r\n\r\nexport default defineNuxtConfig({\r\n\tmodules: [\"@nuxtjs/sanity\",'nuxt-jsonld','@pinia/nuxt','@nuxt/image-edge'],\r\n\tsanity: {\r\n\t\tprojectId: \"say5yn59\",\r\n\t\tapiVersion: '2022-10-14',\r\n\t\tuseCdn:false,\r\n\t\tdataset:process.env.SANITY_DATASET\r\n\t},\r\n\tprivateRuntimeConfig: {\r\n\t\tsanity: {\r\n\t\t\ttoken: process.env.SANITY_TOKEN,\r\n\t\t},\r\n\t},\r\n\tpublicRuntimeConfig:{\r\n\t\tsiteName:'Cool Planet',\r\n\t\tbaseUrl:process.env.BASE_URL\r\n\t},\r\n\ttarget: 'static',\r\n\timage: {\r\n \t\t// Options\r\n \t\tsanity: {\r\n\t\t\tprojectId: 'say5yn59',\r\n\t\t\tdataset: 'production'\r\n\t\t},\r\n \t\tscreens:{\r\n \t\t\txxs:320,\r\n\t\t\txs: 359,\r\n\t\t\tsm: 640,\r\n\t\t\tmd:768,\r\n\t\t\tlg: 1024,\r\n\t\t\txl: 1280,\r\n\t\t\txxl:1536,\r\n\t\t\txxxl:1920,\r\n\t\t\tquadHd:2400,\r\n\t\t\t'4k':3700,\r\n \t\t}\r\n\t},\r\n\tcss:[\r\n\t\t\"@/assets/scss/main.scss\"\r\n\t],\r\n\tvite: {\r\n css: {\r\n preprocessorOptions: {\r\n scss: {\r\n additionalData: '@use \"@/assets/scss/tools.scss\" as *;'\r\n },\r\n },\r\n },\r\n },\r\n alias: {\r\n \"@app\": \"/@app\"\r\n }\r\n})\r\n\r\n```\r\n\r\n### Logs\r\n\r\n```shell\r\nNo logs are available.\r\n```\r\n",[2921,2924,2927],{"name":2922,"color":2923},"3.x","29bc7f",{"name":2925,"color":2926},"pending triage","E99695",{"name":2928,"color":2929},"needs reproduction","FBCA04",15441,"nuxt","closed","Nuxt 3 fails to run fetch or render any components on client side – only works on full page refresh on server","2023-01-19T17:50:23Z","https://github.com/nuxt/nuxt/issues/15441",0.6541013,{"description":2938,"labels":2939,"number":2942,"owner":2931,"repository":2931,"state":2932,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Environment\r\n```\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: bun@1.0.22\r\n- Builder: -\r\n- User Config: devtools, typescript, modules, ssr, app, build, postcss, vite, nitro, supabase, primevue, headlessui, piniaPersistedstate, security, routeRules, runtimeConfig\r\n- Runtime Modules: @nuxtjs/supabase@1.1.6, @nuxtjs/tailwindcss@6.11.3, nuxt-icon@0.6.8, nuxt-typed-router@3.5.1, nuxt-security@1.1.0, @vueuse/nuxt@10.7.2, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0\r\n- Build Modules: -\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-41grgd?file=nuxt.config.ts,app.vue,layouts%2Fdefault.vue\r\n\r\n### Describe the bug\r\n\r\n1. go to the second page (works fine)\r\n2. go to the 1st page again \r\n3. notice how the page content loads before the layout has loaded\r\n\r\nI added a transition and you can see how the transition runs **after** the other page loaded. Even thought, that other page should never appear together at the same time with other Layout\r\n\r\nin the repro I added an `await timeout` to introduce the bug. In my actual case, there is no timeout and i'm not 100% sure why it's happening yet. But clearly, I expect Nuxt to load the layout first and then its slot content (the page)\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2940,2941],{"name":2922,"color":2923},{"name":2925,"color":2926},25695,"Page renders before layout change is done","2024-03-18T07:03:19Z","https://github.com/nuxt/nuxt/issues/25695",0.65697485,{"description":2948,"labels":2949,"number":2954,"owner":2931,"repository":2931,"state":2932,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v21.6.1`\r\n- Nuxt Version: `3.10.3`\r\n- CLI Version: `3.10.1`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.4`\r\n- Builder: `-`\r\n- User Config: `nitro`, `modules`, `svgo`, `image`, `googleFonts`, `alias`, `app`, `typescript`, `devtools`, `devServer`\r\n- Runtime Modules: `@pinia/nuxt@0.5.1`, `@nuxt/content@2.12.0`, `@nuxtjs/tailwindcss@6.11.4`, `@nuxtjs/google-fonts@3.1.3`, `nuxt-svgo@4.0.0`, `@vueuse/nuxt@10.9.0`, `@nuxt/image@1.3.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-eedaaw\r\n\r\n### Describe the bug\r\n\r\nWhen transitioning between pages the scroll position is reset which is expected. However when passing the transition via the prop to \u003CNuxtPage> this reset takes places before the page is actually changed. Also the visibility 'glitches' in before changing the page.\r\n\r\nAlthough I am quite inexperienced I believe this could be related to https://github.com/nuxt/nuxt/issues/2593\r\n\r\nA workaround for me was to pass the transition in the nuxt config instead. To be able to use js hooks I declared them in the prop without specifying a transition name or type:\r\n```\r\n\u003CNuxtPage :transition=\"{onAfterEnter: () => {console.log('onAfterEnter')},}\"/>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2950,2951],{"name":2925,"color":2926},{"name":2952,"color":2953},"pages","00DFB5",26034,"scroll jump & visibility issue with page transitions","2025-04-02T08:45:05Z","https://github.com/nuxt/nuxt/issues/26034",0.6582515,{"description":2960,"labels":2961,"number":2964,"owner":2931,"repository":2931,"state":2932,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\nNuxt project info: 6:37:53 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.15.1\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2, nuxt-monaco-editor@1.3.1, @element-plus/nuxt@1.1.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nThis is my `nuxt.config.js`:\n\n```js\nexport default defineNuxtConfig({\n\tdevtools: { enabled: true },\n\tssr:true,\n\tdevServer:{\n\t\thost:\"0.0.0.0\",\n\t\tport:8001,\n\t},\n\tmodules: [\"@nuxt/ui\", \"nuxt-monaco-editor\", '@element-plus/nuxt'],\n\tplugins:[{\n\t\tsrc:\"~/plugins/router.js\",\n\t\tssr:false,\n\t}],\n\talias: {\n\t\t'css':\"/assets/css\",\n\t\t'font':\"/assets/font\",\n\t\t\"comps\":\"/components\",\n\t\t\"pages\":\"/pages\"\n\t},\n\tcss:[\"css/index.css\"],\n\tcompatibilityDate: \"2024-08-05\",\n})\n```\n\nVery simple, but I found that in the DEV mode, devServer will load the modules' file (in the node_modules) for many times repeatly!\n\nThese 3 modules generated about 2k js files needing to load, which spend about 2minutes to load a page, but when I just modify a little bit part of my code(or just wait for some time without doing anything), the version of the js files changed, so I need to load them again!\n\n\n\nOnly the js files for the 3 modules would be loaded for many times, others wouldn't.\n\n\n### Describe the bug\n\nLike the above, in the loading time, I could do nothing but waiting.There is no response after clicking the link, button or other item.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2962,2963],{"name":2925,"color":2926},{"name":2928,"color":2929},29945,"Extremely slow due to the Nuxt Modules!!! I even can not bear that!","2024-11-16T20:32:02Z","https://github.com/nuxt/nuxt/issues/29945",0.65921354,{"description":2970,"labels":2971,"number":2974,"owner":2931,"repository":2931,"state":2932,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.15.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@8.10.0`\r\n- Builder: `vite`\r\n- User Config: `app`, `modules`, `css`, `colorMode`\r\n- Runtime Modules: `@nuxt/content@2.3.0`, `@nuxtjs/tailwindcss@6.2.0`, `@nuxtjs/color-mode@3.2.0`, `@morev/vue-transitions/nuxt@2.3.5`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\n1. Implement some page transition\r\n2. Apply transition in `out-in` mode\r\n3. Run transition by changing page\r\n4. Change page another time until transition leave active stage is ended\r\n5. Page is broken\r\n\r\nRecreated on StackBlitz: https://stackblitz.com/edit/github-4ngexz?file=app.vue\n\n### Describe the bug\n\nContent of pages is completely disappeared. The only way to fix it is to refresh the page.\r\n\r\nAs I see, Nuxt is not able to create page content in transition enter active stage, because leave active stage was not completed correctly. \n\n### Additional context\n\nI was able to implement a workaround: block any links in `NuxtLink` components for the time transition is active.\n\n### Logs\n\n```shell\nYou can find similar logs in browser console (not in server console):\r\n\r\n\r\nUncaught DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.\r\n at insert (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:7329:12)\r\n at move (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:5938:9)\r\n at move (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:5911:7)\r\n at move (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:5911:7)\r\n at activeBranch.transition.afterLeave (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:2326:15)\r\n at performRemove (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:6025:20)\r\n at el._leaveCb (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:2977:9)\r\n at finishLeave (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:7970:13)\r\n at resolve2 (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:8001:30)\r\n at whenTransitionEnds (http://localhost:3000/_nuxt/node_modules/.vite/deps/chunk-QO6ZHO7P.js?v=e9f66680:8086:12)\r\n```\n```\n",[2972,2973],{"name":2922,"color":2923},{"name":2925,"color":2926},15588,"Fast page transition breaks pages content","2023-01-19T18:34:57Z","https://github.com/nuxt/nuxt/issues/15588",0.661608,{"description":2980,"labels":2981,"number":2986,"owner":2931,"repository":2931,"state":2932,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### Environment\n\nI'm using the env within codesandbox cloud envrionnent but it can be reproduced on any environment.\n\n### Reproduction\n\n- Reproduction Code: https://codesandbox.io/p/devbox/nuxt-empty-pinia-state-race-condition-lv74z2?file=%2Fcomponents%2FMainContainer.vue%3A29%2C10-29%2C22\n\n- Reproduction URL: \n - [Unexpected behavior: with dangling store ref](https://lv74z2-3000.csb.app/WithDanglingStoreRef)\n - [Expected behavior: with accessing store ref from Nuxt plugin](https://lv74z2-3000.csb.app/WithStoreFromPlugin)\n\n- Keep refreshing the page at a rate of 10 times per second until you see an empty store state where the elements are bordered in red.\n\n### Describe the bug\n\nWe had this bug on production after releasing our first Nuxt3 APP. \n\n[Here's the target page with the deployed fix](https://gora.golf.rakuten.co.jp/lesson/school/guide/4685)\n\nThere is a page rendering a child component, both of them running in Nuxt 3 using the Composition API (or options API - it does not matter). The child component has a setup function that contains: `const store = usePostStore()` and other computed props used to display store state values on the UI.\n\nThe page component also has a setup function that contains: `const store = usePostStore()`. The page component also has an `onServerPrefetch` lifecycle hook that makes API calls on SSR. The API calls a function that goes like this:\n\n1. Executes an async fetch operation.\n2. References the store: `const store = usePostStore()`.\n3. Patches the store.\n4. Makes 2 other concurrent API calls async. Each call references the store after each async call is fulfilled, and then patches the store afterwards.\n\n### More Theoretical Analysis on What's happing internally:\n\n- [Mermaid Graphs with in-depth use case scenario trying to depict the root cause of the issue](https://mermaid-js.github.io/mermaid-live-editor/edit#pako:eNq1Wm1T2zgQ_is76dyVzKQcCfeamXamQHtwB5QSev0Q-sGRFaLBtnKSTOBK__utXvyWOLHjuP2QxvFqtS_PrlbP8LVDuE87w84PP8A04Asy84SCm5PbCH8AkPHkTnjzGVwJPgloOL7tuG8wIjTyBOO3nS9OGMBnghLFeAQ3R-mPb8dHgi8kFXBN_42pVF_g9es3cDS-jB8VjEbX2fp0O_wVt8JPePdAIwXnnM_zGwEcGSXHXy_pItELxzxS9FF9y4kdG7GT8VnEFPMC9h-FKxYxD0aKC_plRfLd-JiHcx7pTS94HCkW3eWlUgvfXp2hhfgJx14QyKJxACdG2_v-OJGAfqnAIBMYlAocZgKHRYH3fSPxZ3-sY2D8wUhMqaARoUuiAys6qCF6aEUPq0X_tAac9sdW7MpTZLYkYjc-HWwQsRueHq4ToZFfloB_YooJwE80z0PQPTD1tJyF0z682n_15vksIjySTCqd1k9z31NUPsNZLtcjhb8tLR5sXFyUPawve2b8fcYdAwonnvKe4a_xpzN0I_KpWOd59t18W67PEQ9iXXgYkjOfekH6Q2V5_l1enucV5TmoqM9zo-Wiqj4vjNjleIR1huHYgLdLI_mhRiVbnVdbVPJgUyl_MOo-ri9lJ7C-lJ3A-lL-2IcfUYH-OHTowD6cC8QzXBYW2GBcFypv2SwnUyi9ZcucTKH2isatr75BZflda7eutVvXzq3jkuoYbS7DkV15roWVq5ebpvVCAk_KEzqFuTvFpiwIhi-mU4L_elIJfk_14wH-c4-vFsxXs-Fg_tgjPOBi-ALfLauTrtqcPkK0xlTfwcHvW-pjGBChPIxIopD-Mp3mFB4cpI9rFOZVJsd34nbhXdIpUieKb0fXPcxyT0M3tWpZYqBFBlpmkBcyYlIXP0L4hHkInTBN0BwHDUbYXDv5CdtP6YsLj0WICXJf-tb0HtN6StcyIrjy5P3HmMa0VCRgk_ghDRUYO169eZPuOkxbVx9s3zGB2rth5B763XRdugAXp0YN4RJHK8CWS9kDlXB6c3OFT0ZfujKV1tsWDB7CFcdOsbfwmG5dMOUCzn76kNu0IF40-104x3KsMM8J1fIeAUSolNoQ6_2g3Pu8DY-UxFi0EHDPP8fFPNqrDJn2uVTGpGoIIo4-MzVzJ8neXhewOUwpti3dGfa62QZmQVlUBQ-ZpEAExZbigxf5mJU73ZUE9VeWu30vqVpwcQ98ToUFQch1UhUHNUNNPsw5D3LBXBOULKJv5VNEbMNzIT3s1spYERKp792GmIqsZ_VwpeOOTxLm2FW1hiSaU_w_s2VdFHMoyldD0ZFaiBxgPWLCRDzPVeTP3erwu2KMcCwpLchtcZlTPqI4_PkFuAM1RaBNnCDGIrkJ23pUSuOZj0iC1XVhPeJqljiCrvEFzLwHmuYoWsaurIFTj1CdbZ8Z40_oAw34PNRntI31L92a7aUElAka8jFdj5SJ9i7xIfFyO7S6qEoL00k-XOsMeM8EwsxJvZSrQQSp8GhOgrxOjcNEpidb7wWSZ8vrNo4B6GkpoDnY_9rdOsrLbWHFzFV3id1WB1GHplYCEjQLmg1IOgOpM1VeOxjgpumSl7JEbWVpmvEWoYCDCcl6v66y2rZYHXM9IuPSBZ5CBaP8Yuuq7P96oF3N5W-757IauVkq93waeE_U77aSzv726ew3SuexwLZE8JbLpNQuH5t82q4uTZpEcnPaIat9l1XYk_qu3q3OrvNkX1_xTAe1Sf19zbm0lLjVNu5OD2yCakaZyOuvlbCLOFAMUw1hIiThXy1moY81T2IhdFPPnw11ApbGV6LuR9Q3QZRRGpU06E1qwljZXYETbYp2lcdozhR9n1OiizS5QNzWqHJbU0tjwR_d2s0VMy6LrcKO79ouixG5FvKbCyc5zWy0ViFfM2DSuDjBdh2iKSxHN1WtN4OEsd1nU5O8tElgK5lS8kSCJJu5UF9y3A9HXZHp7eWvOI4kyvNAm5bmRp0lVggHBo-k-HctWoJnippYmf06uu1g_SEF9BBuZhSosS9A-_Ql2HUhz4hm2O_BYsbQCOJFEOihHsf7LFrOCGlqZ6nNyP2KmK0M4hl3BUcU5zXGxVYKLGOmEOVGSaLR2IWeaawkEujXBIvK9hCLoNCLvDsaWhAEDFegIgwMhiJzCsfIyA9Qy_52lpkdclQoQf2uSdt5dKVLayhLhrdlm5FpHBHbFvKZsJazot4eUImNgmFLfAI_Nh0E8bhtOv6J6UuZo7Jg9IQ7hFvpOKF6mkOznuBGoACakigWmWJpFINvhHNhR_OVW-VeWge3i70rJjh1mRvC5xmNVsOt8ZFMQSwqAXlPw6XE7pDdzRQeTmrJbNBnXmw5vZ5JmTm2TNbwAMKKyTcrc66aHK3QQ-Xc0AZiaAMrVEUJreWDGpFBDZmgpjRQTQ6oDgHUiP3ZnvqpvF83J312YXx2ont24HqaEz27sDytUTy78DsNyZ1mzM7WsNua02lO6LTF5uxK5VR3iY1X0kYMTjv0TRvczW7ETXPWpnZM2-BrWiBrWmFqdqZpdudodiRoGqetITXTAi_TCinTFiPTHh3TjItpmYj5PixMGxRM6_xLM_LlezEv7dAuO3EurREunV4npCL0mN8Zdr5qxbcdxFpIbztD_Op74v62cxt9QzkvVnyEA2VnqERMex3B47tZZzjFcwmf7B3MXacSEYqHPxcX9k_9zF_8ffsfkFVhxA)\n- Please trying uncommenting some of the graphs and commenting the rest to check different perspectives.\n\n### Here is the catch\nAccessing the page shows the post data correctly from the store state in the child component template. Sometimes, though, after refreshing the page at a fast rate, the child component renders an empty/stale state of the store. I could reproduce this in two different apps by having this code flow and logic steps.\n\n### How we quickly solved this?\nIn the async function that gets triggered in the `onServerPrefetch` of the page component, we moved the store ref to be hoisted at the root of the function.\n\n### Other solutions:\n- Seems to be that somehow the context is lost when this line is executed in the child component `const store = usePostStore()`, which can happen when the micro-task queue has unfulfilled requests.\n- Delaying the rendering of the child component until the data is fully loaded from the page, can solve it, as it ensures that the `const store = usePostStore()` gets the resolved context that was updated from/after any async operation\n- Accessing store reference through a plugin [like here](https://lv74z2-3000.csb.app/WithStoreFromPlugin):\n```\nimport { defineNuxtPlugin } from \"#app\";\nimport { usePostStore } from \"../store\";\n\nexport default defineNuxtPlugin((nuxtApp) => {\n nuxtApp.provide(\"store\", usePostStore());\n});\n```\n- On SSR, the flow is ok, but on the client the state is lost\n\n### Additional context\n\nTried bumping version of the following dependencies but it did not solve the issue:\n- Node\n- Nuxt\n- Vue\n- Pinia\n\n### Logs\n\n- For SSR logs: please check the console here: https://codesandbox.io/p/devbox/nuxt-empty-pinia-state-race-condition-lv74z2?file=%2Fcomponents%2FMainContainer.vue%3A29%2C10-29%2C22\n\n- For Client side logs: https://lv74z2-3000.csb.app/main",[2982,2983],{"name":2925,"color":2926},{"name":2984,"color":2985},"possible regression","B90A42",29718,"Nuxt Context Contamination","2024-11-04T13:29:31Z","https://github.com/nuxt/nuxt/issues/29718",0.66300887,{"description":2992,"labels":2993,"number":3000,"owner":2931,"repository":2931,"state":2932,"title":3001,"updated_at":3002,"url":3003,"score":3004},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.7.1`\r\n- CLI Version: `3.8.3`\r\n- Nitro Version: `2.6.3`\r\n- Package Manager: `pnpm@8.7.5`\r\n- Builder: `-`\r\n- User Config: `extends`, `app`, `spaLoadingTemplate`, `runtimeConfig`, `modules`, `vueuse`, `i18n`, `ssr`, `vue`, `nitro`, `vite`, `build`, `typescript`, `devtools`\r\n- Runtime Modules: `@pinia/nuxt@0.4.11`, `@nuxtjs/i18n@8.0.0-beta.10`, `@vueuse/nuxt@10.4.1`, `@unocss/nuxt@0.55.7`, `@nuxtjs/fontaine@0.4.1`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nusing nuxt config\r\n```\r\napp: { pageTransition: { name: 'fade', mode: 'out-in' }, }\r\n```\n\n### Describe the bug\n\nWhen page transition is enabled on nuxt 3.7.1 it leaves the previous page and adds new page at the bottom and initial it renders two page top one is the actual page but buttom one stucks at loading \r\n\r\n[Here you can try the deployment with pageTransition](http://app-v2-bmih98l5k-hubble-excahnge.vercel.app)\r\n\r\n[Here you can try the deployment with pageTransition false](http://app-v2-a81c5iagp-hubble-excahnge.vercel.app)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2994,2995,2996,2997],{"name":2922,"color":2923},{"name":2925,"color":2926},{"name":2928,"color":2929},{"name":2998,"color":2999},"closed-by-bot","ededed",23141,"3.7.1 pageTransition breaks","2023-09-20T01:47:41Z","https://github.com/nuxt/nuxt/issues/23141",0.6634803,{"description":3006,"labels":3007,"number":3012,"owner":2931,"repository":2931,"state":2932,"title":3013,"updated_at":3014,"url":3015,"score":3016},"### Environment\r\n\r\n\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.2\r\n- Nitro Version: 2.6.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: vue, site, imports, image, runtimeConfig, app, css, typescript, modules, vueuse, colorMode, vite, elementPlus, plugins\r\n- Runtime Modules: @vueuse/nuxt@10.4.1, @pinia/nuxt@0.4.11, @element-plus/nuxt@1.0.5, @nuxtjs/color-mode@3.3.0, @nuxtjs/color-mode@3.3.0, @unocss/nuxt@0.55.1, @nuxt/image@1.0.0-rc.1, nuxt-lodash@2.5.0, nuxt-simple-sitemap@3.2.6, nuxt-swiper@1.2.2\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nno need\r\n\r\n### Describe the bug\r\n\r\nAfter running 'run build' and executing it with Node.js, an error occurred.\r\nWhen I use 'dev', it can successfully fetch data.\r\n[nuxt] [request error] [unhandled] [500] Cannot read properties of null (reading 'allow_product')\r\nallow_product in Front\r\n```js\r\nconst Front = setFront() \r\nif (!Front) {\r\n const result = await getSetting()\r\n Front.value = result.data\r\n}\r\n```\r\nI tried using state management to reduce duplicate requests and save expenses.\r\nI'm not sure if there's a better way to do it.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3008,3009,3010,3011],{"name":2922,"color":2923},{"name":2925,"color":2926},{"name":2928,"color":2929},{"name":2998,"color":2999},23025,"[bug] cant fetch data","2023-09-14T01:47:28Z","https://github.com/nuxt/nuxt/issues/23025",0.6647833,{"description":3018,"labels":3019,"number":3023,"owner":2931,"repository":2931,"state":2932,"title":3024,"updated_at":3025,"url":3026,"score":3027},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v21.6.2\n- Nuxt Version: 3.13.0\n- CLI Version: 3.13.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: devtools, experimental, runtimeConfig, routeRules, app, css, plugins, modules, proxy, googleFonts, primevue, tailwindcss, compatibilityDate, vite\n- Runtime Modules: nuxt-proxy-request@1.10.0\n- Build Modules: -\n```\n\n### Reproduction\n\n\n\n```\nconst queryParams = computed(() => {\n const params = {\n ... state.pagination,\n ...state.filters,\n };\n\n return Object.fromEntries(\n Object.entries(params).filter(([_, value]) => {\n return (\n value !== undefined &&\n value !== null &&\n !(Array.isArray(value) && value.length === 0)\n );\n })\n );\n});\n\n\nconst { refresh } = await useFetch('/api/search', {\n lazy: false,\n watch: false,\n server: true,\n params: queryParams,\n onResponse({ response }) {\n products.value = response._data.products;\n },\n});\n```\n\n### Describe the bug\n\nNuxt 3 SSR\n\nHello, tell me what could be the matter - when I reload the page via F5, the data is first written to products, and then after 1 second it is immediately written to an empty array. If I go via NuxtLink, the data does not disappear until I reload the page again via f5\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3020,3021,3022],{"name":2925,"color":2926},{"name":2928,"color":2929},{"name":2998,"color":2999},29628,"useFetch overwrite data to empty value on page reload","2024-10-30T02:01:04Z","https://github.com/nuxt/nuxt/issues/29628",0.6666592,{"description":3029,"labels":3030,"number":3037,"owner":2931,"repository":2931,"state":2932,"title":3038,"updated_at":3039,"url":3040,"score":3041},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.2`\r\n- Nuxt Version: `3.11.1`\r\n- CLI Version: `3.11.0`\r\n- Nitro Version: `2.9.4`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `ssr`, `pages`, `debug`, `typescript`, `modules`, `devtools`, `runtimeConfig`, `colorMode`, `tailwindcss`, `purgecss`, `eslint`, `i18n`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.11.4`, `nuxt-purgecss@2.0.0`, `nuxt-headlessui@1.1.5`, `@nuxtjs/i18n@8.2.0`, `@nuxtjs/color-mode@3.3.3`, `nuxt-icon@0.6.9`, `@nuxt/image@1.4.0`, `@nuxt/content@2.12.1`, `vue3-carousel-nuxt@1.1.0`, `@nuxtjs/device@3.1.1`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n- Start nuxt app using yarn dev (SSR mode)\r\n- Manually/directly browse to a page (using url) **(1)**\r\n- Navigating to another page through a NuxtLink element **(2)**\r\n- Navigating back to the initial page through a NuxtLink element **(3)**\r\n\r\n### Describe the bug\r\n\r\nWhen the page at **(1)** is opened, everything is rendered correctly. After browsing to another page **(2)** and then back to the initial page **(3)** the initial page no longer has any content (like the previous state disappeared). The content/state is visible in the nuxt devtool widget, yet it is not rendered, and the client reports that the data object in the initial page **(1)** is undefined. No errors / warning / debugging messages are shown anywhere (neither in the client or the server).\r\n\r\n### Additional context\r\n\r\nThe data object in the page described at **(1)** looks like this:\r\n```\r\nlet categories = await findAll\u003CICategory>('categories', {\r\n locale: languageToLocale(locale.value),\r\n populate: '*',\r\n requestKey: 'static-content-categories',\r\n});\r\n```\r\n\r\nThe object is then used in the `\u003Ctemplate>` block to display some fields, using plain elements.\r\n\r\nThe findAll() function simply calls function queryApi() that internally uses useAsyncData(). The findAll/queryApi functions are part of a custom composable (added under composables/ directory).\r\n\r\n```\r\nasync function queryApi (entity: string, requestParams: IApiRequestParams) {\r\n const {\r\n data,\r\n pending\r\n } = await useAsyncData\u003CIApiResponse>(\r\n requestParams.requestKey,\r\n async () => $fetch(makeApiEndpointQueryUrl(entity, requestParams), {\r\n method: 'GET',\r\n headers: {\r\n 'Content-Type': 'application/json',\r\n 'Accept': 'application/json',\r\n },\r\n })\r\n );\r\n\r\n return {\r\n data: data.value?.data ?? undefined,\r\n meta: data.value?.meta ?? undefined,\r\n };\r\n }\r\n```\r\n\r\nAdditional methods used in queryApi (part of the same composable):\r\n\r\n ```\r\nfunction makeApiEndpointUrl (entity: string): string {\r\n return useRuntimeConfig().api.url + '/api/' + entity;\r\n }\r\n\r\n function makeApiEndpointQueryUrl (entity: string, requestParams: IApiRequestParams): string {\r\n let query = qs.stringify(requestParams, { encodeValuesOnly: true });\r\n return makeApiEndpointUrl(entity) + '?' + query;\r\n }\r\n```\r\n\r\nThe interfaces presented in the example are exported from types/index.d.ts.\r\n\r\nAll in all it seems that things are starting to break after the first render (coming from the server), when the app goes in SPA mode. If I use `\u003Ca>` tags instead of `\u003CNuxtLink>` everything works correctly, the only downside being that the app no longer offers the SPA feeling (as pages get refreshed).\r\n\r\n### Logs\r\n\r\n_No response_",[3031,3032,3033,3034],{"name":2922,"color":2923},{"name":2925,"color":2926},{"name":2928,"color":2929},{"name":3035,"color":3036},"⛔️ can be closed","484893",26409,"Strange behavior when using NuxtLink","2024-05-24T14:34:00Z","https://github.com/nuxt/nuxt/issues/26409",0.66680753,["Reactive",3043],{},["Set"],["ShallowReactive",3046],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSto26EqsEb_4pFC08oJoEk1ikmqmephCIrqREEsw6Fc":-1},"/nuxt/nuxt/31613"]