When we deploy a new version, it takes some time before our users see the updated version as our assets (js, css, images, etc.) keep the same filenames between releases and get cached by browsers. I suggest fixing this by adding a hash to the filenames generated by Webpack.
Since we're using .net 9 now in designer, it's possible that if vi migrate to new MapStaticAssets method, that we will solve the caching issues.
Optimizations in serving static files could be found here
Description
When we deploy a new version, it takes some time before our users see the updated version as our assets (js, css, images, etc.) keep the same filenames between releases and get cached by browsers. I suggest fixing this by adding a hash to the filenames generated by Webpack.
https://webpack.js.org/guides/caching/