swr routes throw 404 on consecutive requests + generated html is not cached

[warflash]

Environment

---

• Operating System: Windows_NT
• Node Version: v16.13.2
• Nuxt Version: 3.0.0-rc.11
• Nitro Version: -
• Package Manager: npm@8.13.2
• Builder: vite
• User Config: -
• Runtime Modules: -
• Build Modules: -

---

Reproduction

https://github.com/warflash/nuxt_swr
https://nuxt-swr.vercel.app/

Describe the bug

There's probably two distinct bugs here, not 100% sure. Can open another issue if required.

Deploying the above repro to vercel returns x-vercel-cache: MISS even after multiple refreshes, eventhough swr is enabled for all routes in the nuxt config. Additionally spam refreshing results in nuxt returning an error page This page is temporarily unavailable.

I have not tested this for different deploy targets so might be vercel related

Additional context

No response

Logs

No response

[danielroe]

Would you try again with rc12? We released a number of changes to nitro, including some changes to swr caching.

[warflash]

Sure, updated the repro and live deployment to rc12. The 404 issue seems resolved from what I can tell, still no caching with swr -> x-vercel-cache: MISS. But that's expected I guess as unjs/nitro#545 is still pending

[danielroe]

For caching on Vercel, you can set the following route rule:

'/**': { cache: { swr: true, maxAge: 120, staleMaxAge: 60, headersOnly: true } },

[Neuvier]

On vercel, the swr cache is working when i refresh the app with F5, but not when i come from an internal nuxtlink where i still see external API calls ?

[danielroe]

@Neuvier You will need to set experimental.payloadExtraction to enable extracting api calls.

[Neuvier]

@Neuvier You will need to set experimental.payloadExtraction to enable extracting api calls.

It's working, Thanks so much !