Brian Beard

I am also seeing this in production. As for how to reproduce with @bardobrado's repo, the following may help: - throttle the connection to 3g (fast or slow) in chrome...

FYI: Not that this issue shouldn't be fixed on the sapper side of things, but I couldn't reproduce this issue with svelte-kit.

I think I have found the solution. - Move `%sapper.scripts%` within `src/template.html` from the `head` to the end of the `body`. The reason why 0.28.0+ was because https://github.com/sveltejs/sapper-template/pull/247/commits/d4c75af7f2392af1a635210ef6da4581f7713a7f#diff-4b1d306eb7949b768a10a68600e5973cdcbeafa0827e6f6e3c78c55269d4cc0b . I...

It is also worth repeating in this thread that a more elegant solution, suggested by @benmccann, is wrapping your sapper.start() in a window load event listener. ```js // src/client.js window.addEventListener('load',...

I am also sporadically hitting this error. Any updates on this?

For those of you who want to use v2 now, I have created a temporary npm package until v2 support is merged in this repo. `npm install -D @babeard/svelte-heroicons@next`

Defer or not doesn't seem to affect the hydration/duplication problem unfortunately. I'm not sure why because spec says that deferred scripts are `fetched in parallel and evaluated when the page...

> I'm also questioning now whether the document not being loaded yet would result in the behavior being seen. My original hypothesis may be totally incorrect, but the two fixes...