Matteo Rigoni

As stated above, this is not yet tested but is a first implementation straight out of my head. Need help with testing properly in a netlify environment

Was able to setup a test environment here https://nitro-deploy-swr-test.netlify.app/api/hello?querytest=test3 by forking nitro-deploys repository. First attempt at implementing the feature was a failure, apparently Netlify disregard _headers file when setting cache...

I've added headers to the generated localCall response instead of appending them to the incoming request event. This works on my tests, not sure if this is the correct implementation...

A note on `netlify-edge` preset: I've added the same headers to the response, did not test them for now. It's not clear from the article whether edge functions caching strategies...

ATM, Cache headers behaviour is not as predictable as ODB behaviour. Meaning it doesn't return stale content as you would expect. Opened an issue [here](https://github.com/netlify-labs/cache-control-and-swr/issues/1) and a support ticket [here](https://answers.netlify.com/t/netlify-new-swr-cache-policy-behaviour-is-not-clear/104747)...

If I use a nitro task in, let's say, Netlify will it leverage netlify background functions?

@shilman any news on this? Just kick started a vue 3 project and storybook doesn't seem to pick up types of the props. It would be a blast if, when...

Upgraded, did not infer types from the component anyway. Let me know if I can help more!

Sure! Take a look here: https://github.com/Rigo-m/sb-nuxt-types-repro

FYI: using only `defineProps` doesn't fix the situation. Defaulting every prop with `withDefaults` compiler macro exposes every prop (doesn't infer type, but at least docgen reads the props). I guess...