Persistent storage between deployments

[bitttttten]

Hello!

I am using Netlify to host a gatsby website that is a PWA and offline-friendly (using gatsby-plugin-offline). Whenever I update my website, a lot of the old assets are removed. Assets like JS bundles, CSS, and media. When people then come back to the website after an update, a lot of the website breaks until the service worker has updated and they have refreshed the tab. Not a great user experience.

This isn’t a Netlify problem, it can happen on any platform. Previously I solved this on other platforms by uploading my assets to something like S3 and then referencing the files from the website there. However, I wanted to keep everything inside Netlify and I can’t find the best solution for this. I just need persistent storage that I can write to, or to persist storage between builds. What is the best solution with Netlify?

Many thanks!

[fool]

Yup, this is a pretty common use pattern. So common we wrote up the best practices around it:

[Common Issue] Why do I see “Uncaught SyntaxError: Unexpected token <” errors? How can I use chunking or versioning for my assets at Netlify?

The error Uncaught SyntaxError: Unexpected token < is most commonly caused by your site’s code referring to an asset that is no longer available. Most commonly, this is due to a filename change in assets generated during your build. The same situation happens if you use versioned or chunked javascript where the filename changes with every deploy. Let’s look at an example: A file that was named /assets/main-123abc.js would change to /assets/main-431def.js – where there is a variable hash inc…

Take a look and let me know if you can adapt to that workflow. If not, I don’t have any better suggestions, but your use case could help inform our future developments around this workflow so I am asking for a reason