How does a vue single-page project force a refresh of resources after a release?

question: how does a vue single-page project prompt the user to refresh the page after the release?
A single-page application is not like an ordinary website, where resources are reloaded every time the page jumps. If the user opens the page before releasing the new version and stays in the page without refresh, then the user will not see the content of the new version.

what we did before is to build a version.js, to use the request interceptor in axios, intercept every request, request version.js, in the interceptor, and then compare the content in the version.js with the existing local one, and prompt the user if it is inconsistent.
is there a better way than the above?

Single-page-application version-releases vue.js html5

Feb.15,2022

static resource service, in cookie , insert the version number or hash ,
access, compare, inconsistent, do a redirect,

if an API request is made, put the version in the request header information, and the backend receives it. After comparison,
returns an error message if it is inconsistent, and the front end makes a pop-up prompt or redirect it.

can you post the code of this practice you said?
it is not very clear to request version.js in interceptor

Previous: Can Vscode select multiple lines and then increment the number in turn?

Next: Why does vue.js need to refresh the page before it can be displayed when updating the avatar?

How does a vue single-page project force a refresh of resources after a release?
question: how does a vue single-page project prompt the user to refresh the page after the release? A single-page application is not like an ordinary website, where resources are reloaded every time the page jumps. If the user opens the page before r...

Single-page-application version-releases vue.js html5

Feb.15,2022