\r\n```\r\n\r\nNuxi info:\r\n```\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v21.6.1\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.26\r\n- Builder: -\r\n- User Config: extends, modules, future, experimental, runtimeConfig, scripts, i18n, routeRules, ignore, site, app, ogImage, sitemap, plausible\r\n- Runtime Modules: @nuxt/scripts@^0.6.4, @nuxtjs/seo@2.0.0-rc.19, @nuxtjs/tailwindcss@^6.12.0, @vee-validate/nuxt@^4.13.2, nuxt-og-image, @nuxtjs/plausible@^1.0.2\r\n- Build Modules: -\r\n------------------------------\r\n```",[],251,"icon","On dev: 404 for icons that were not visible on initial page load","2024-09-05T14:04:26Z","https://github.com/nuxt/icon/issues/251",0.73722017,{"description":2065,"labels":2066,"number":2068,"owner":1994,"repository":1994,"state":2025,"title":2069,"updated_at":2070,"url":2071,"score":2072},"The problem that im facing has to do with nuxt-link and nuxt-view. As far as i've used vuejs i remember that if you put router-link and down below you put a router-view it will render everything with navigation bar if its there. However with nuxt i put nuxt-link (or router-link for testing) and below i put nuxt-view (or router-view for testing) it redirects me to another page but the navigation bar dissapears. At first i was told that i might need to use layout instead of components but its pretty much the same result. Here is the code:\r\n\r\n \r\n \u003Ctemplate>\r\n \u003Cdiv id=\"\">\r\n \u003Cnuxt-link :to='{name: \"terms-sections-test1\"}'>Go to 1 \u003C/nuxt-link>\r\n \u003Cnuxt-link to='/terms/sections/test2'>Go to 2 \u003C/nuxt-link>\r\n \u003Crouter-link to='terms/sections/test1'>ROUTER LINK\u003C/router-link>\r\n\r\n\r\n \u003Cnuxt-view> \u003C/nuxt-view>\r\n \u003Crouter-view >\u003C/router-view>\r\n\r\n\r\n\r\n \u003C/div>\r\n \u003C/template>\r\n \u003Cscript>\r\n export default {\r\n /* eslint-disable */\r\n layout: 'navigation'\r\n\r\n }\r\n \u003C/script>\r\n \u003Cstyle lang=\"css\" scoped>\r\n \u003C/style>\r\n\r\nIs there a work around so that i dont have to include layout everytime in its children components? or i need to include them everywhere? sorry for the noob question but i cant really see good documentation for nuxt-view.\r\n\r\nP.S: everytime when i press on my first nuxt-link it redirects me to the page but when i go back to initial page (the code above) it gives me this warning:\r\n\r\n [Vue warn]: Unknown custom element: \u003Cnuxt-view> - did you register the component correctly? For \r\n recursive components, make sure to provide the \"name\" option.\r\n\r\nPlease help :)\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/c977\">#c977\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2067],{"name":2048,"color":2049},1116,"Nuxt-view with nuxt-link","2023-01-18T15:40:45Z","https://github.com/nuxt/nuxt/issues/1116",0.7372647,{"labels":2074,"number":2077,"owner":1994,"repository":1994,"state":2025,"title":2078,"updated_at":2052,"url":2079,"score":2080},[2075,2076],{"name":2004,"color":2005},{"name":2048,"color":2049},9797,"after call error method in fetch navigation not working","https://github.com/nuxt/nuxt/issues/9797",0.73824656,{"description":2082,"labels":2083,"number":2092,"owner":1994,"repository":1994,"state":2025,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.13.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `app`, `ssr`, `srcDir`, `modules`, `vite`, `nitro`, `googleFonts`, `i18n`, `content`, `plausible`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.6.5`, `@pinia/nuxt@0.4.7`, `@nuxtjs/google-fonts@3.0.0`, `nuxt-icon@0.3.3`, `@nuxtjs/i18n-edge@8.0.0-beta.10-28003311.2c39470`, `@nuxt/content@2.5.2`, `@nuxtjs/plausible@0.2.0`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nI was not able to create a minimal reproduction for this issue as this bug does not seem to occur in a minimal example. So here is how you can reproduce it:\r\n\r\n```sh\r\ngit clone --recurse-submodules https://github.com/WolfgangDrescher/lassus-tricinium-project.git demo\r\ncd demo\r\ngit checkout bb55ac1\r\nnpm install\r\nnpx nuxi upgrade --force # currently it will upgrade to nuxt v3.3.3\r\nnpm run build\r\nnode .output/server/index.mjs\r\n```\r\n\r\nCompare this to the working example with nuxt v3.3.1:\r\n\r\n```sh\r\ngit clone --recurse-submodules https://github.com/WolfgangDrescher/lassus-tricinium-project.git demo\r\ncd demo\r\ngit checkout bb55ac1\r\nnpm install\r\nnpm run build\r\nnode .output/server/index.mjs\r\n```\r\n\r\n\r\n### Describe the bug\r\n\r\nCSS and JS files are missing the the `\u003Chead>` when building my project with `npm run build`. In development mode everything works as expected. When I lock nuxt to `v3.3.1` it also works as expected but using `v3.3.2` or above the build will not have css styles for example (some global styles that are not `scoped` are displayed though). This is why I think it must be a bug related to nuxt but I'm unsure. Debugging this for quite a while it could also be related to Vite or `@nuxtjs/tailwindcss`.\r\n\r\nFirst I thought that https://github.com/nuxt-modules/tailwindcss/issues/628 might be the problem but this does not seem to be the case.\r\n\r\nMaybe `vite` was updated in nuxt `v3.3.2` so the production build is bundled different?\r\n\r\n### Additional context\r\n\r\nNuxt v3.3.1:\r\n\r\n\u003Cimg width=\"1104\" alt=\"Bildschirm颅foto 2023-04-04 um 18 02 33\" src=\"https://user-images.githubusercontent.com/865594/229855320-94c7abbf-179d-4344-8a50-148a099babec.png\">\r\n\r\nNuxt v3.3.3:\r\n\r\n\u003Cimg width=\"1103\" alt=\"Bildschirm颅foto 2023-04-04 um 18 05 02\" src=\"https://user-images.githubusercontent.com/865594/229855428-1ca85c5b-fc40-4662-84ca-f094a00dae31.png\">\r\n\r\n\r\n### Logs\r\n\r\nThe only error message I get is this `importScripts is not defined` related to a web worker. I don't think this can be the problem. Maybe if the Vite build somehow fails after this. But no errors in the console when while building. And still nuxt `v3.3.1` works just fine.\r\n\r\n```shell-script\r\nverovio-85527134.js:1 Uncaught ReferenceError: importScripts is not defined at verovio-85527134.js:1:1\r\n```\r\n",[2084,2085,2086,2089],{"name":2034,"color":2035},{"name":2007,"color":2008},{"name":2087,"color":2088},"upstream","E8A36D",{"name":2090,"color":2091},"upstream-bug","B60205",20091,"Missing `\u003Clink>` tags in production build","2023-04-20T14:41:11Z","https://github.com/nuxt/nuxt/issues/20091",0.74150926,{"description":2098,"labels":2099,"number":2102,"owner":1994,"repository":1994,"state":2025,"title":2103,"updated_at":2104,"url":2105,"score":2106},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.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: npm@9.5.1\r\n- Builder: -\r\n- User Config: devtools, app, routeRules, experimental, runtimeConfig, modules, build, alias, dir, piniaPersistedstate, gtag, vite\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.10.3, nuxt-icon@0.4.2, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, nuxt-gtag@1.1.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nRun the app using Nuxt version 3.9.0 and navigate to any route\r\n\r\nCheck it out the live version using 3.9.0\r\n[https://capacithor-git-nuxt-390-igortrinidad.vercel.app/](https://capacithor-git-nuxt-390-igortrinidad.vercel.app/)\n\n### Describe the bug\n\nThe page transitions and layout rendering broken after the update, for some reason the component SiteFooter appears above the layout \u003Cslot /> on any route client route change, but it renders properly on server side rendering (hard refresh)....\r\n\r\n\n\n### Additional context\n\n\r\n\r\nlayouts/default.vue\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"w-screen h-full min-h-[100vh]\">\r\n \u003CSiteHeader />\r\n \u003Cslot />\r\n \u003CSiteFooter />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n import SiteHeader from './site-components/SiteHeader.vue'\r\n import SiteFooter from './site-components/SiteFooter.vue'\r\n\u003C/script>\r\n```\n\n### Logs\n\n_No response_",[2100,2101],{"name":2034,"color":2035},{"name":2004,"color":2005},24944,"[3.9.0] Client rendering and page transitions broke after updating to the newest Nuxt version","2024-01-03T19:46:15Z","https://github.com/nuxt/nuxt/issues/24944",0.7439453,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"bCgT6VwLOnFdlHBO5FKHLxNdP_l8hXvL1YVmr9JoYUE":-1},"/nuxt/nuxt.com/994"]