Fighting the browser cache in deployed websites

[rallisf1]

Is your feature request related to a problem? Please describe.
Many browsers (especially chrome mobile) don't respect the caching TTL set by hosts. This leads to changes made in existing symbols to not be visible by guests, even after that TTL, unless they clear their browser history.

Describe the solution you'd like
Add the build time timestamp as a file suffix on exported _symbols.

Describe alternatives you've considered
I am currently either duplicating symbols, so their id changes, which is not that helpful when being used in many pages; or setting a no-cache, no-store, must-revalidate Cache-Control header on the host.

[MentalGear]

would you be able to add a PR for this?

[rallisf1]

would you be able to add a PR for this?

I don't think there will be any new commits/PRs to this puppy. I'm using it as it is for now, probably will do a hard fork next year.

[MentalGear]

Really unfortunate: such a great idea and so much potential and energy already put into it, but very understandable as open-source economics are really tough to figure out. This would have needed some kind of supabase-branded CMS kickstarter or so to get it rolling in the same FOSS spirit.

PS: I'm wondering if Primo v.2 would be eligible for the new Sveltehack 2024 contest (previous winner Superforms), certainly could bring much value to the Svelte community, but it's just not known enough.