Prompt Updates

[n-ce]

Implementation

• A user-side update request can be registered with vite-plugin-pwa.
• It can be implemented as a modal.
• We can pass in a description containing a full-size scrollable changelog.
• The changelog can be stored separately in a text file or Markdown file, which can be fetched.

Advantages :

• Makes the user aware of an available update.
• Makes the user aware of the new features and fixes.
• Gives the user control over when to update.

  Disadvantages (over automatic update) :

• Requires an extra user action.
• Increases the size of the shipped code.

[n-ce]

Totally Forgot about this https://vite-pwa-org.netlify.app/guide/auto-update.html

😥😥 Now have to figure out a way to migrate without losing user data.

[n-ce]

Okay here's the plan so far : I will implant a swDetonator in the latest production with an if condition that will detonate it only when it detects a commit message that contains the string 'detonate'. Then prod will not receive any updates for X amount of time. Then when X time finishes, I will release the new sw for production with the commit containing the string 'detonate'. Here X amount of time denotes the Service Worker Cache retention time. Having this time range before detonation will ensure all users are on the latest version to support detonation.