Problems with webpack packaging updates

for example, the last time I packaged a project, the name js was abc.js. Then I packed it this time, put the packaged files on the server, and then opened the unupdated website in my browser before I put it on the server. Well, after I updated this version, because the last js file has been deleted, the page opened by my browser can no longer be clicked, because the js files are gone, so it has to be refreshed before the browser reloads my new js file. How to solve this problem. It is possible to load new js files without refreshing them.

Apr.25,2022

this is a problem of website update strategy. Static resources that may be used by users cannot be deleted immediately, so hash is usually injected into the file name of static resources. If you update the content of the website, run npm run build , then publish the static resource now, and then release the * .html file, and then usually wait one night, and then clear the files with duplicate file names. The one with the earlier date of removal.


before you publish a new resource, the user opens the web page and loads static resources such as js, and then you publish it, and the user will not be able to click. It should not have an impact, after all, the static resources required by the current page have been loaded into memory, all the functions of the current page should be able to use normally. The next time the user enters this page, the latest resources should be loaded.

Menu