Currently we have a Hydrogen instance on production running via Netlify. On top of that, we are also fetching content from Storyblok. You can see the result on www.horando.de – the website itself runs smoothly and the metrics are very good. We love Hydrogen!
But we investigated an error, which comes up everytime we trigger a new deployment on Netlify. We are using webhooks on Storyblok and when content is published or unpublished, we always trigger a new build on Netlify. Sometimes, when there are a lot of changes, we have a higher amount of triggers in the queue. See the following screenshot:
If a deployment is ready, and you are opening up the website the first time, we see the following error:
In the console you can see a list of errors, the most interesting one is in the lowest position. If we click on it we see the following results:
So like I said, this only happens when we trigger a new build. If you see the error page und just refresh the page, the error is gone, which leads me to think about that it might be a caching problem and the cache gets also refreshed while refreshing the website.
I have opened up a similar discussion on the support forums of Hydrogen and the developers state that this is not only bound to Hydrogen. It is a general problem on Netlify and also happens e.g. on Gatsby.
I have the feeling, that the index.html file as the entry point gets cached by the servers of Netlify and the header of the file does not get updated after a new build, so the browser still uses the old file, with the old reference of an older js file, with older imports of wrong file hashes.
So any ideas to fix that?