Right now after an update is pushed the old PWA site can still be cached. There is no mechanism to inform the user of updates.
At minimum I should try and find a way to automatically invalidate the cache and update after a production deploy, but long term I may want to make this user facing so they can choose to update when ready.
Right now after an update is pushed the old PWA site can still be cached. There is no mechanism to inform the user of updates.
At minimum I should try and find a way to automatically invalidate the cache and update after a production deploy, but long term I may want to make this user facing so they can choose to update when ready.