Timestamp in query filenames can break site for current users

[hecktarzuli]

Environment

Nuxt 3.5.0 Nuxt Content 2.6.0

Reproduction

Generate a site using Nuxt content, then run generate again. Notice the built query files change even though you did nothing.

Describe the bug

• You are on a site that uses Nuxt Content, it either was deployed recently, or doesn't get much traffic (so not all files are in the CDN)
• A new deploy is sent while you are on the site
• When you go to a new page, the site could break since the query file you needed no longer exists at the origin.

This is likely related to timestamps in the built query files. Are they really needed? The filenames should only change when their content changes.

Additional context

No response

Logs

No response

[juliangerhards]

Much bigger problem when scaling to multiple servers.... Are there any updates? How to get rid of the timestamp?

[hecktarzuli]

@juliangerhards related: https://github.com/nuxt/nuxt/issues/24940#event-12904965854

For us, since we have boat-loads of servers, we just toss our assets into S3 so they are guaranteed to always exist.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 30 days with no activity.