Build uses outdated files from cache since 5.1.6 or 5.1.7

[jachang820]

Astro Info

Astro                    v5.1.8
Node                     v22.12.0
System                   Windows (x64)
Package Manager          npm
Output                   static
Adapter                  none
Integrations             @astrojs/sitemap
                         @astrojs/svelte

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

If a script is written (e.g. a Shiki transformer or Rehype plugin) that changes something in a content post, then the site is built, then script is changed to do something else, and the site built again. That second build seems to think that because the content file hasn't been updated, nothing has changed, and the changes aren't written to the cache.

For example, I add the following:

// astro.config.mjs
export default defineConfig({
    site: SITE_URL,
    integrations: [sitemap(), svelte()],
    markdown: {
        shikiConfig: {
            transformers: [{
                line(line, index) {
                    line.properties['style'] = 'background-color: red';
                    return line;
                }
            }]
        }
    }
});

Then I run npm run build. Then I delete the line line.properties['style'] = 'background-color: red';. Then I build again and preview. The line backgrounds will remain red.

I have tested this on StackBlitz and it's reproducible, but I don't have a Pro account and can't share the project.

What's the expected result?

I expect that npm run build will always output the latest version of the project. In the case above, I expect that the content files are updated to not have lines with red backgrounds if npm run build is executed after that line has been removed.

Link to Minimal Reproducible Example

N/A, read above

Participation

• I am willing to submit a pull request for this issue.

[ascorbic]

Thanks. It should be using the Astro config as part of the cache key, so it should certainly not be behaving as described. You don't need a pro account to share a reproduction. If you use https://astro.new/repro then you can create one that is shareable.

[github-actions]

Hello @jachang820. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs repro will be closed if they have no activity within 3 days.

[jachang820]

I'm assuming you mean a link like this: https://stackblitz.com/edit/github-141451nv

The problem is whenever someone spins it up again, it deletes previous builds in the /dist directory, and it will recognize the script the first time. So whoever who runs it needs to delete (or add) a line and rebuild to see what I'm talking about.

[ascorbic]

OK, thanks. The issue is that it compares the serialised config, and the part you changed was in a function so wasn't serialised. You can try changing e.g. the site value at the same time and see that it does update. We may need to hash the actual file contents instead, though that will need some things to be changed.