You're viewing the Inertia.js v2.0 documentation. Upgrade guide →

Upgrade guide for v2.0

You can find the legacy docs for Inertia.js v1.0 at v1.inertiajs.com.

What's new

Inertia.js v2.0 is a huge step forward for Inertia! The core library has been completely rewritten to architecturally support asynchronous requests, enabling a whole set of new features, including:

Additionally, for security sensitive projects, Inertia now offers a history encryption API, allowing you to clear page data from history state when logging out of an application.

Upgrade dependencies

To upgrade to the Inertia.js v2.0, first use npm to install the client-side adapter of your choice:

npm install @inertiajs/vue3@^2.0

Next, upgrade the inertiajs/inertia-laravel package to use the 2.x dev branch:

composer require inertiajs/inertia-laravel:^2.0

Breaking changes

While a significant release, Inertia.js v2.0 doesn't introduce many breaking changes. Here's a list of all the breaking changes:

Dropped Laravel 8 and 9 support

The Laravel adapter now requires Laravel 10 and PHP 8.1 at a minimum.

Dropped Vue 2 support

The Vue 2 adapter has been removed. Vue 2 reached End of Life on December 3, 2023, so this felt like it was time.

Router `replace` method

The previously deprecated router.replace method has been re-instated, but its functionality has changed. It is now used to make Client Side page visits. To make server-side visits that replace the current history entry in the browser, use the replace option:

router.get('/users', { search: 'John' }, { replace: true })

Svelte adapter

  • Dropped support for Svelte 3 as it reached End of Life on June 20, 2023.
  • The remember helper has been rename to useRemember to be consistent with other helpers.
  • Updated setup callback in app.js. You need to pass props when initializing the App component. See setup in app.js
  • setup callback is now required in ssr.js. See setup in ssr.js

Partial reloads are now async

Previously partial reloads in Inertia were synchronous, just like all Inertia requests. In v2.0, partial reloads are now asynchronous. Generally this is desirable, but if you were relying on these requests being synchronous, you may need to adjust your code.