jsakamoto

@fingers10 Thank you for the report! The crawler maybe encountered a `mailto://` link. I'll fix it, and moreover, I'll consider once again how to traverse hyperlinks more carefully than before.

@fingers10 I released the fixed version v.1.0.0-preview.22.0 just now. - https://www.nuget.org/packages/BlazorWasmPreRendering.Build/1.0.0-preview.22.0 I appreciate it if you try it out. Again, I'd say many thanks for your contributions!

@fingers10 If my memory is correct, your project is a PWA with offline support, right? If so, that experience may be caused by a service worker's script. The default implementation...

@fingers10 > In PWA apps, index.html always loads the stale content even though published index.html has new content. Is there any way to forcibly fetch index.html from server when online...

@fingers10 > In general while publishing, if is enabled, will it be good to replace loading text only in index.html and for remaining paths like /about/index.html can we replace loading...

@fingers10 > And is there any other way we can avoid flickering effect when directly opening any routes other than index.html because index.html will have same content before and after...

@fingers10 First of all, basically, please remember that this package is my hobby project using my free time, so I can't spend much time. And, I'm a native Japanese speaker,...

@fingers10 > Do all the consumers of app needs to enable update on reload for this to take effect? No, all the consumers of apps usually do not need to...

@fingers10 I could not reproduce the error that you said.😥 I upgraded `Microsoft.AspNetCore.Components.WebAssembly` and `Microsoft.AspNetCore.Components.WebAssembly.DevServer` to 6.0.6 on my some Blazor WebAssembly app projects and re-published them, but all of...

@fingers10 Thank you for informing me about that behavior with the very understandable report! I immediately understood this problem due to your detailed description and a short video.👍 Anyway, as...