search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
34.8k stars 9.83k forks source link

[Blazor] Update service-worker registration to prevent caching issues #44635

Open javiercn opened 1 year ago

javiercn commented 1 year ago 
    I think we should change our templates to do `serviceWorker.register('...', { updateViaCache: 'none' })`

Originally posted by @javiercn in https://github.com/dotnet/aspnetcore/issues/39252#issuecomment-1283783747

We might also want to modernize the service worker and use ES modules (now supported) instead of plain scripts as they allow dependencies to be stated explicitly.

guardrex commented 1 year ago

WRT docs ... I'll resolve it for releases up to .NET 8 with the text that I mentioned on the other issue. If this is adopted for .NET 8, I'll refactor the text for .NET 8 or later to say that it's the default.

ghost commented 1 year ago

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost commented 9 months ago

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost commented 6 months ago

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.