Ensure menu data is re-used across requests

[fago]

After first-page load, the menu data is available, e.g. due to state-hydration. When navigating around pages, the menu data should not be re-fetched (unless language changes later on)

[TurtlBbx]

Cache support for useFetch/useAsyncData is not supported internally/out-of-the-box in Nuxt at the moment, as you can see in this open issue: https://github.com/nuxt/nuxt/issues/15445.

Solutions:

• We could implement a custom cache logic, but that's not ideal.
• Solve it on project level, we could move menu components inside app.vue in projects, that way menus wouldn't get re-fetched on client side navigation and would need to be manually re-fetched when needed (e.g. language change). That would mean that we have menus on top level - app.vue, but we can also render menus inside different layouts (NuxtLayout) with named slots, so there shouldn't be any downside.

[fago]

@TurtlBbx what about keepalive? https://vuejs.org/guide/built-ins/keep-alive.html

[fago]

@TurtlBbx this is actually fixed by having the component in the layout https://github.com/drunomics/lupus-decoupled-nuxt3-demo/commit/f54c44808a1858d5aeaf669acca2290063db1eba

moving breadcrumbs in the layout breaks things though, a new bug.