Ngô Đức Anh

Yeah this is an age-old issue, but I have not investigated it. Sounds like something is being unexpectedly cached, though.

@timohausmann no, let's keep it open. Dev mode is supported, and as such, we will need it to work properly. This clearly causes it to not.

@Xardasus if you use `installSerwist` + `runtimeCaching` like in basically any Next.js example in the docs, please disable `runtimeCaching` in development mode: ```ts runtimeCaching: process.env.NODE_ENV === "development" ? undefined :...

@mi-hol fine by me :) I'll add the labels myself, perhaps. Then we can try using some sort of workflows that automatically add those labels when a new issue is...

Here are blogs related to caching: - https://serwist.pages.dev/docs/serwist/guide/precaching - https://serwist.pages.dev/docs/serwist/runtime-caching - https://serwist.pages.dev/docs/serwist/core/serwist Well, seems that you want to precache some files. I notice that you use Next.js, so there's a...

@userquin ah, well, that file is only meant for development purposes. We expect the users to extend `SerwistGlobalConfig` themselves. Well, for now, at least. Though, since that is only for...

@userquin huh, thanks for the info :) Will investigate soon!

Sorry for the late reply. I'm currently focused on [Serwist 9.0.0](https://github.com/serwist/serwist/discussions/66), so things can escape my attention at times. Before I go into the details, I just want to say...

@mdevils can you verify if "/offline.html" was properly cached? Thanks! Also, you may want to check if `matcher` did match the request that was made to the non-existent resource. I...

@AhmedBaset can you check if "/offline.html" is in the Cache storage? Thanks! There was a bug in which using navigation preload caused Serwist to not handle precached files properly.