When creating a custom cache handler, is it possible to fall back to the default behavior?
Unanswered
Highlander posted this in #help-forum
HighlanderOP
Re: things like https://caching-tools.github.io/next-shared-cache/usage/opt-out-cache-on-build#configuration-steps, where one can provide multiple possible handlers.
Rather than slow down all requests for connection timeout duration or something, or just not have any caching mechanism at all, is it possible to say "fall back to the default, inbuilt NextJS behavior"? How?
handlers: [handler1, handler2],
Rather than slow down all requests for connection timeout duration or something, or just not have any caching mechanism at all, is it possible to say "fall back to the default, inbuilt NextJS behavior"? How?
1 Reply
HighlanderOP
I'm fine if the answer deviates from Nescha stuff.
It just seems to be the default recommendation in the docs.
My current understanding is it's an all-or-nothing swap.
It just seems to be the default recommendation in the docs.
My current understanding is it's an all-or-nothing swap.