You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I'm building a static site with npm run generate, caching is pointless and just hindering my development flow.
I've read about cacheProvider: 'none' here: storyblok/storyblok-js-client#10
But this is not working for me. I still get cached content in my dev server.
The only thing that's working for me is very unconvenient.
Hi @marekmaurizio it was closed because there has been no activity since 2021. Most of the issues get solved in newer versions. So if it's still an issue feel free to re-open it with a reproduction link so we can prioritize it and make a fix if there is one.
Storyblok SDKs are open source, meaning that you can also contribute if you like to solve the issue.
Since I'm building a static site with
npm run generate
, caching is pointless and just hindering my development flow.I've read about
cacheProvider: 'none'
here: storyblok/storyblok-js-client#10But this is not working for me. I still get cached content in my dev server.
The only thing that's working for me is very unconvenient.
having to provide a
cv
prop for every request is really bothersome.The text was updated successfully, but these errors were encountered: