Asset versioning

One common challenge when building single-page apps is refreshing site assets when they've been changed. Thankfully, Inertia makes this easy by optionally tracking the current version of your site assets. When an asset changes, Inertia will automatically make a full page visit instead of a XHR visit on the next request.


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 the version method of the Inertia HandleInertiaRequests middleware.

class HandleInertiaRequests extends Middleware
    public function version(Request $request)
        return parent::version($request);
The HandleInertiaRequests middleware provides a sensible default for Laravel applications, which uses either a hash of the "app.asset_url" configuration value or the "mix-manifest.json" file. When using Vite, Inertia will use a hash of the "build/manifest.json" file.

Alternatively, the asset version can be provided manually using the Inertia::version() method.

use Inertia\Inertia;

Inertia::version(fn () => $version); // Lazily...

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.

If you're using Laravel Mix, you can do this automatically by enabling versioning in your webpack.mix.js file. When using Laravel's Vite integration, asset versioning is done automatically.