It is not possible to exactly do what you are asking, but our assets are already technically served from the cache. Even though chrome network tab doesn't explicitly say this, here is how you can evaluate.
When you initially load genesys.min.js, it will download the full file reflecting the full file size in the network tab traffic logs.
Then on the subsequent page reload, it will not download the full file but serve from the cache, technically soft-caching as shown in the below image where you can see only 327 bytes fetch in the network logs for this file.
It will download the full file again when anything changes in our assets, for example when we do a new release it will automatically reflect for you without any delay because a soft-cache check is performed that will let browser know to re-download.
Hi @Ranjith_Manikante_Sa ,
thanks for the info, now the behavior is more clear.
This cache is actually working in tandem with our prefetch since the second file downloaded is the 300ish Byte one and not the 97 kB one.