However in some cases, scripts can contain dynamic parts (mostly inline scripts and script localization). This can cause issues, because Swift Performance will use the hash of the script file as a file name, and when scripts are regenerated but content is a bit different, it will produce a different hash – and a different file.
You can exclude problematic scripts from merging, or alternatively you can use Separate Scripts feature.
If you enable this feature Swift Performance will generate separate scripts for all cached pages. It can increase a bit the cache size, however it won’t produce abandoned script files, so in long term cache size will be smaller.