Published responses cached regardless of caching settings

[nathobson]

Describe the issue you're facing

Responses from the Storyblok API are cached when retrieving published content, even when apiOptions contains a cache type of none.

Reproduction

https://stackblitz.com/edit/withastro-astro-971qsd?file=.env

Steps to reproduce

Using Astro in SSR mode via output: 'server' and the Node adapter in mode: standalone, responses from the Storyblok API are cached when retrieving published content, even when apiOptions contains a cache type of none.

For example, the following call via useStoryblok() will return the cached response, not reflecting any updated (published) content:

const story = await useStoryblok(`cdn/stories/home`, {
    version: "published",
  }
)

I've also tested with the settings as in playground-ssr in the repo, which has the following settings:

apiOptions: {
  cache: {
    clear: "auto",
    type: "memory",
  },
}

This produced the same result.

However, if the exact same useStoryblok() call is set to retrieve drafts, everything updates when the page is refreshed, including draft and published content:

const story = await useStoryblok(`cdn/stories/home`, {
    version: "draft",
  }
)

There appears to be a closed and merged PR from three weeks ago in the storyblok-js-client repo but for whatever reason, this doesn't seem to have fixed the issue in the Storyblok Astro SDK.

Tested with the latest release (v5.0.2) of @storyblok/astro, which appears to contain the latest release of storyblok/storyblok-js-client from looking at the version installed in node_modules.

System Info

System:
    OS: macOS 15.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 66.47 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
    bun: 1.0.22 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 130.1.71.114
    Chrome: 129.0.6668.103
    Safari: 18.0.1
    Safari Technology Preview: 18.0

Used Package Manager

npm

Error logs (Optional)

No response

Validations

• Follow our Code of Conduct

[J05HI]

Any news here @dipankarmaikap ?

I am using the new content layer feature and getting the same problem.
If I unpublish a page it is still in the collection. I have disabled the cache.
Here's my content/config:

import {storyblokLoader} from '@storyblok/astro';
import {defineCollection} from 'astro:content';
import StoryblokApi from '../utils/StoryblokApi';


const storyblokCollection = defineCollection({
    loader: storyblokLoader({
        accessToken: import.meta.env.STORYBLOK_TOKEN,
        version: StoryblokApi.getVersion(),
        apiOptions: {
            cache: {
                type: 'none',
            },
        },
    }),
});

export const collections = {
    storyblok: storyblokCollection,
};

[J05HI]

Replacing the same asset with a new version (for example when using the storyblok web image editor) the cache does not get refreshed too.

[dipankarmaikap]

Hi @J05HI,

Thank you for reporting this! Please note that the Storyblok Astro Content Layer API is still in its early experimental phase. We wouldn’t recommend using it in production just yet, but we truly appreciate you trying it out and providing feedback to help us improve.

[edodusi]

Hi @nathobson, the behavior you are facing reflects the current cache behavior in Storyblok, it's not that something isn't working, it's actually how it's supposed to work.

The storyblok-js-client is trying to offer users tools to implement a custom caching strategy, but in order to benefit from it you have to first understand how it works and what are these tools.

I tried to cover everything in this FAQ page: https://www.storyblok.com/faq/how-stories-are-cached-content-delivery-api

This should give you many possibilities to implement your own strategies. As stated in the FAQ, you can always bypass the cache helpers in the client, if you understand the impact on the rate limits.

I hope this helps.

cc @J05HI