mind your cache

[adsick]

Hi, I'm trying to learn Leptos right now, but when I tried to run it's examples on a local machine I've seen just the leftovers from some eframe stuff I was doing before. When I refreshed the page that stuff was still there despite active Trunk with a Leptos app. Only force update helped (Ctrl+Shift+R).

I'm not saying that there is anything wrong with this template, but I encountered some confusion so I decided to share it. Also I know that there is code in this repo that is responsible for making cache work, maybe it's not 100% correct? is it possible to only ship it in release builds?

Browser: Firefox 113.0.1

[coderedart]

I often get confused by this too. This is why there is a warning in the README about caching behavior and how to get around this.

assets/sw.js script will try to cache our app, and loads the cached version when it cannot connect to server allowing your app to work offline (like PWA). appending #dev to index.html will skip this caching, allowing us to load the latest builds during development.

[fdb]

Thanks for posting this. In my app it doesn't make sense to have a service worker so I just deleted that <script> in index.html.

[justinlovinger]

Note, the cache was disabled in #102, so this issue can be closed. In fact, the service-worker currently does nothing but throw harmless errors.