v0.6.8

• Reintroduce inertia.ssr.enabled config option (#488)
• Fix bug where SSR is dispatched twice when errors exist (#489)

v0.6.7

• Report SSR errors (#486)
• Auto enable SSR based on existence of SSR bundle (#487)

v0.6.6

• Add inertia:start-ssr and inertia:stop-ssr artisan commands (#483)

v0.6.5

• Add Laravel v10 support (#480)

v0.6.4

• Add PHP 8.2 support (#463)

v0.6.3

• Check Vite manifest path (build/manifest.json) when determining the current asset version (#399)

v0.6.2

• Switch to using the Vary: X-Inertia header (#404)
• Fix bug with incompatible $request->header() method (#404)

v0.6.1

• Set Vary: Accept header for all responses (#398)
• Only register Blade directives when actually needed (#395)

v0.6.0

Automatic redirects

Since returning a Redirect::back() response is such a common pattern within an Inertia app, this adapter now does this automatically for you when no response is returned from a controller (#350).

For example, consider this teams controller which redirects back to the previous page after updating a team. With this new feature you can now omit the Redirect::back() response and it will happen automatically.

class TeamsController extends Controller
{
    public function update(Team $team)
    {
        $team->update(/* ... */);
-
-       return Redirect::back();
    }
}

You can disable this behavior, or even do something entirely different, by adding an onEmptyResponse method to your HandleInertiaRequests middleware:

use Illuminate\Http\Request;
use Symfony\Component\HttpFoundation\Response;

/**
 * Determines what to do when an Inertia action returned with no response.
 * By default, we'll redirect the user back to where they came from.
 *
 * @param  Request  $request
 * @param  Response  $response
 * @return Response
 */
public function onEmptyResponse(Request $request, Response $response): Response
{
    // Use the default Laravel "empty" response
    return $response;
}

Fixed

• Fixed namespace issue with Route::inertia() method (#368)
• Added session check when sharing validation errors (#380)
• Fixed docblock on facade render method (#387)

v0.5.4

Find release notes here.