Forcing Reloads (not a chapter)

[philsturgeon]

This should probably fit in somewhere in the book, or maybe be part of a new chapter, but the idea to mention this concept popped into my head today.

Where could we put a thing about how to update your client when important changes happen?

There is a) hot reloads, but also b) you need to log in again, and we are gonna do an actual refresh.
See image below

This example from asana is not just "you are logged out" but "there have been significant deployments so you ned a new session". Some folks do this when they get a lot of 500 errors, or of course lots of 403s, but there is often a more proactive approach with maybe a BFF or more general API having awareness of releases? I have vague memories of telling frontend devs to do this but i cannot remember qwhat we did.

For mobile users there is also "You need to update your application". This could happen if errors have a Sunset header on them for example, but what other signs are there?

[mbifulco]

• suddenly we detect loss of connection (loads of 500 errors, etc) and we realize we need to do something to update
• using git commit hash to detect
• React Error boundaries to track when things start falling apart - provide an interface saying: we know this is bad, we logged this and it will get attention, and here’s how you talk to support if you need it; otherwise, go ahead and refresh