-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cesiumWorkerBootstrapper does not have cache busting #9057
Comments
Doesn't this apply to all files in the library that are served statically and fetched at runtime? And that could be something the application can handle based on how you're serving those files/by serving them under a folder like |
True. yet, cesium is a bit different. since This also can be seen on every cesium installation guide, especially with https://cesium.com/docs/tutorials/cesium-and-webpack/ See the lines here : new CopywebpackPlugin([ { from: path.join(cesiumSource, cesiumWorkers), to: 'Workers' } ]), So normally you are correct, the app installing the library should take care of the hashing and caching of the files, but some files in cesium are required to be fetched by cesium, so cesium library expects the files to be exist. Also most of the files under |
@mramato are you aware of this? I've looked into the gulp file and I saw that |
Our distro, C137.js can help with this issue since you can cache bust the single file. |
+1 seeing this issue still in 1.97.0 Any thoughts on this? |
Still working on what could be a solution here. |
Latest cesium version has changed the file
cesiumWorkerBootstrapper
yet under Build/Cesium/Workers/ the file
cesiumWorkerBootstrapper
does not have cache busting, i.e no hash to this file. most other files seems ok.which caused to latest version to break until hard refresh is done.
The text was updated successfully, but these errors were encountered: