You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm.. a client side navigation has no way of knowing it is out of date, except from the response.. and we fetch JS in parallel. Unless they have setup some background pinging of versioning I don't see how Next could ever know this. My understanding was that Vercel keeps previous deploys around. Its also possible I suppose that that fetch data before JS and in that case they could know, of course that would be very inefficient.
In any case this is an idea and if anyone has ideas on how to implement it we can consider making a request.
Duplicates
Latest version
Current behavior 😯
I have Page1 and Page2 if i change something on Page2 and then using Page1 to navigate to Page2 i get error
I guess its due to the hash of the file name change but my current client session still working with V1 until i do hard refresh.
Is there any plan to work around this?
Expected behavior 🤔
Page2 should load without issue even if changes have been made and pushed to prod
The text was updated successfully, but these errors were encountered: