Handling old browser versions after deployment
Hey *,
we are facing issues due to browsers out in the wild running on older versions of our frontend. We encountered 2 scenarios each having bugs, which get fixed after hard reloading the browser.
1. old version of the code -> hard relaod need to get the bug fix after deployment
2. wrong env config value -> hard reload needed to get the updated env config
Now we are looking for a solution to have nuxt handle it, since we can not rely on our user base performing hard reloads in the browser.
To me it feels this must be a common issue in any real world nuxt app. What mechanism does come nuxt with to solve this?
Cheers
we are facing issues due to browsers out in the wild running on older versions of our frontend. We encountered 2 scenarios each having bugs, which get fixed after hard reloading the browser.
1. old version of the code -> hard relaod need to get the bug fix after deployment
2. wrong env config value -> hard reload needed to get the updated env config
Now we are looking for a solution to have nuxt handle it, since we can not rely on our user base performing hard reloads in the browser.
To me it feels this must be a common issue in any real world nuxt app. What mechanism does come nuxt with to solve this?
Cheers
