Configuration
To enable automatic asset refreshing, you need to tell Inertia the current version of your assets. This can be any arbitrary string (letters, numbers, or a file hash), as long as it changes when your assets have been updated. Typically, your application’s asset version can be specified within theversion method of the Inertia HandleInertiaRequests middleware.
Inertia::version() method.
Cache Busting
Asset refreshing in Inertia works on the assumption that a hard page visit will trigger your assets to reload. However, Inertia doesn’t actually do anything to force this. Typically this is done with some form of cache busting. For example, appending a version query parameter to the end of your asset URLs. With Laravel’s Vite integration, asset versioning is done automatically. If you’re using Laravel Mix, you can do this automatically by enabling versioning in yourwebpack.mix.js file.
Manual Refreshing
If you want to take asset refreshing into your control, you can return a fixed value from theversion method in the HandleInertiaRequests middleware. This disables Inertia’s automatic asset versioning.
For example, if you want to notify users when a new version of your frontend is available, you can still expose the actual asset version to the frontend by including it as shared data.
version property and show a notification when a new version is detected.