topic Avoiding the need for users to Empty Cache and Hard Reload in Splunk Dev

Avoiding the need for users to Empty Cache and Hard Reload

apc — Mon, 30 Jun 2025 21:23:52 GMT

Greetings!

I lead the development for 3 interactive React/SUIT apps, and before I go down a rabbit trail testing a few ideas, I wondered if anyone had already found something that might suit my requirement.

Essentially, when promoting a new version (with some added feature(s), etc.) to Production, users have to open their browser's Dev tools, long-click on the browser's Reload button, and select "Empty Cache and Hard Reload". Understandably, they do not like having to take this step.

I have some ideas around incrementing file names to avoid this, but just thought I'd check here to see if anyone else had already come up with a method.

Thanks!

Re: Avoiding the need for users to Empty Cache and Hard Reload

livehybrid — Tue, 01 Jul 2025 06:11:25 GMT

Hi @apc

It sounds like you need to increment the "build" value in the [install] stanza of app.conf:

build = <integer> * Required. * Must be a positive integer. * Increment this whenever you change files in <app_name>/static. * Every release must change both 'version' and 'build' settings. * Ensures browsers don't use cached copies of old static files in new versions of your app. * 'build' is a single integer, unlike 'version' which can be a complex string, such as 1.5.18.

🌟 Did this answer help you? If so, please consider:

Adding karma to show it was useful
Marking it as the solution if it resolved your issue
Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

Re: Avoiding the need for users to Empty Cache and Hard Reload

apc — Tue, 01 Jul 2025 11:57:11 GMT

Thanks, @livehybrid - wasn't even aware of that param. I'll give that a shot and reply here with results the next time I promote a new version.