This definitely gets the job done, but updating the references on each release could get cumbersome.Īs I'm sure we're not the first ones to deal with this, I figured I would throw it out to the community. Our current thought is to simply attach a version number onto the name of the JavaScript files and then when changes are made, increment the version on the script and update all references. Obviously, on a support call, we can simply inform them to do a ctrl F5 refresh to ensure that they get the up-to-date files from the server, but it would be preferable to handle this before that time. ECMAScript 2018 finalizes the full implementation of the Promise object with Promise.finally: Example let myPromise new Promise () myPromise.then() myPromise.catch() myPromise.finally() Promise. That being said, one issue we are running into is that after we push out an update with new JavaScript files, the client browsers still use the cached version of the file and they do not see the update. We are currently working in a private beta and so are still in the process of making fairly rapid changes, although obviously as usage is starting to ramp up, we will be slowing down this process.
0 kommentar(er)
