additional caching strategies for data fetching composables

[danielroe]

For data fetching composables, we offer initialCache which can either be switched on or off. But in some cases, users may have more advanced strategies, such as refetching after a certain time period or when the tab is reactivated.

Some use cases:

• users may wish to use the same data (e.g. not refetch) for requests made within a certain time window: allow manually redirecting to 404 route within a dynamic slug #13788
• data stored/synced to session storage: useFetch cache is lost after hibernation #14360
• users may wish to force a refresh even if there is a pending request: useAsyncData refresh can not be called until promise is resolved #13300

[pi0]

Related PR and description: nuxt/framework#3985

initialCache flag was introduced in nuxt/framework#3985 as a way to revert the effect of the change we have. It is not a caching strategy.

We could have another issue for force-fetch or track via (#2973). It is not a caching strategy exactly either and removed in same nuxt/framework#3985 PR to be supported back via a better API and also cancel support.

More I think higher-order composables or asyncData handlers with a cache wrapper can provide caching strategies for fetcher. The handler can return the cached value. And such wrapper could be more veastile than having a built-in fixed implementation of cached functions i was initially proposing in nuxt/framework#3985.