For now, you can avoid passing a reactive route slug to useFetch. To resolve, we can look at ensuring the route is synced in layout suspense forks (though this will be tricky).

For now, you can avoid passing a reactive route slug to useFetch. To resolve, we can look at ensuring the route is synced in layout suspense forks (though this will be tricky).

thx @danielroe, i modified the stackblitz without any reactive route params in the useFetch. The behavior is still the same.

Workaround has no effect.

const { data } = await useFetch( 'https://chroniclingamerica.loc.gov/search/titles/results/', { params: { terms: 'oakland', page: 1, format: 'json' } } );

I was looking at #21585 but i think that does not solve this problem

@danielroe can you please remove the workaround label, removing the reactivity from useFetch does not make any difference.

@c-schwan

Why not just use definePageMeta({ layout: 'empty' }) in the empty.vue page instead of using <NuxtLayout /> there too, which is already used in app.vue.

I think that fixes the issue for you.

@c-schwan

Why not just use definePageMeta({ layout: 'empty' }) in the empty.vue page instead of using <NuxtLayout /> there too, which is already used in app.vue.

I think that fixes the issue for you.

that's true in this cause, but im using multiable slots in layout or is there a way to pass content to a different slot in layout without using NuxtLayout?

You can define the <NuxtLayout /> in the pages (passing different slots), and remove it from app.vue.

In your page, it would be something like

<!-- /pages/empty.vue -->
<template>
  <NuxtLayout name="empty">
    <template #slot1>...</template>
    <template #slot2>...</template>
  </NuxtLayout>
</template>

@prashantpalikhe thx for help, but then i have to define it on each page (with default layout). this causes the problem that i loose the keepalive state navigating between default layout pages