sveltejs
caching when running `yarn dev`: livereload continues to reload page but same content is "stuck"
Using chromium on archlinux, I've been developing an app for a week now.
However this scenario keeps happening frequently: I'm developing and there's a bug in my code. I keep changing the code to try to fix the bug and the page keep reloading but nothing changes. I get confused and frustrated and then I realise that even though the page is reloading, it's not reloading any of my source code changes. Despite the "reload", it's just continuously reloading a version of the code it's stuck on.
The only way to get it to see my changes is to close the browser window and reopen it.
It's gotten to the point where I've gotten paranoid about my svelte app. Whenever there's a bug I keep closing the window and opening a new one because I can't trust what I'm seeing. It leads me to feeling really negatively about the development experience.
I wonder if sirv is missing some headers to stop chromium from caching the page?
Sometimes shutting and reopening the window doesn't work either. I've reloaded my browser several times and the page just won't update :( I had to hold down shift and hit reload this time, there's definitely some caching issues going on here.
I have the same Issue. It worked fine the most of the time. The first time it helped to restart the computer. But not anymore.
@AmmonStretz It's so annoying right? Not being able to trust what you're seeing. Every single time there's a bug now I don't know if I've already fixed it or not.It's so frustrating I'm regretting not going with Vue 3 beta instead of Svelte haha.
@antony There's no real way to reproduce it in a few steps, just develop for a few hours in any project and eventually it'll get stuck. I think sirv --dev just isn't using the right headers to stop browsers caching.
I've been developing with Sapper for years and I've never seen this. I wonder what the difference in headers is.