Hi Davy,
Sorry for the delay.
We have validated your query related to the browser cache and the issue can be to reproduce in the Blazor WebAssembly application.
We would like to let you know that, the static webassets will always be cached in the browser when we using Blazor WebAssembly application since the resources are loaded in the browser side for rendering.
So, we suggest you to set the HTTP header with no-cache option in your server configuration to resolve this problem. Please refer to the below Github thread and ASP.NET forum for more details.
Note: Once you configured, please clear the browser cache then run the app. after that you didn't need to force cache clear
Regards,
Jesus Arockia Sankaran S