Home/ Questions/Q 4077644
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T17:34:33+00:00

Part of the application we are developing is about to be provided to the

  • 0

Part of the application we are developing is about to be provided to the third-party websites as a widget with a simple code like:

<script src="ourdomain/script.js" type="text/javascript"></script>
<div id="our-id"></div>

Is there any way to provide the workaround for the cases when we update the script.js code fixing, for instance, critical bugs, and on the next load user doesn’t have caching to prevent him to get the new version?

In the other words, is there any analog to timestamp etags in this case?

Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well one way (not the best) is to force them to load the script on each load, so no caching is happening

    <script type="text/javascript">
    document.write("<script src='ourdomain/script.js?" + (new Date().getTime()) + "' type='text/javascript'></script>");
</script>
<div id="our-id"></div>

    The other could be an iframe that loads all the assets from your site, so if you update the JS you can give it a unique name so it forces the browser to get it

    • 0