Skip to content



Inertia and Vite are a great match. Both provide an excellent developer experience and a very productive set of tools to work on a full-stack, modern Laravel monolith.

This documentation provides information about setting up Vite and Inertia together, which, rest assured, is a trivial process.

Initial setup

Using the preset

The simplest way of scaffolding a new Laravel application using Inertia and Vite is to apply the distributed preset on a fresh Laravel installation.

> composer create-project laravel/laravel vite-inertia
> cd vite-inertia
> npx @preset/cli apply laravel:inertia

This preset is a script that adds and configures Vite, Inertia, Tailwind CSS and Pest. Once this command has finished, everything is ready and you can start developing.


If you are used to the conventions from the Inertia ecosystem, you may notice some changes:

  • The main entrypoint is resources/scripts/main.ts instead of resources/js/app.js
  • Pages are stored in resources/views/pages instead of resources/js/Pages
  • Components are stored in resources/views/components instead of resources/js/Shared
  • Layouts are stored in resources/views/layouts instead of resources/js/Layouts
  • File and directory names use kebab-case instead of StudlyCase
  • Inertia pages components can be referenced using dots instead of just slashes

We strongly recommend following these conventions, as it creates the foundations for a consistent and organized architecture.

Don't like these defaults?

You can easily create your own Inertia preset by extending laravel-presets/inertia. Learn more about extending presets in its documentation.

Alternatively, you can use the --no-tailwindcss or --no-pest flags to skip their installation.

From scratch

If you don't want to use the preset, for instance if you are using Laravel Breeze or Jetstream, we recommend following the official Inertia documentation and then switching from Webpack to Vite using our quick start guide. It's not much, but it's honest work.

Serving pages


Inertia requires you to provide a resolve function that takes a page name as a parameter and returns a page component.

With Webpack, the standard way of doing that is by using the require statement, which bundles every specified component thanks to globs.

With Vite though, you must use import.meta.glob or import.meta.globEager to instruct Vite which files to bundle.

Example implementation

If you used the distributed preset, this is already done for you. Otherwise, you can import { resolvePageComponent } from 'vite-plugin-laravel/inertia'.

Here is a minimal example:

 * Imports the given page component from the page record.
function resolvePageComponent(name: string, pages: Record<string, any>) {
	const path = Object.keys(pages)
		.sort((a, b) => a.length - b.length)
		.find((path) => path.endsWith(`${name.replaceAll('.', '/')}.vue`))

	if (!path) {
		throw new Error(`Page not found: ${name}`)

	return typeof pages[path] === 'function'
		? await pages[path]()
		: pages[path]

// Creates the Inertia app, nothing fancy.
  resolve: (name) => resolvePageComponent(name, import.meta.glob('../views/pages/**/*.vue')),
  setup({ el, app, props, plugin }) {
    createApp({ render: () => h(app, props) })

Asset versioning

Inertia has a versioning feature that forces a hard-refresh when an asset change is detected.

You can notify Inertia of such a change by giving the manifest's hash to Inertia's version method, either in its default middleware or via its facade.

// app/Http/Middleware/HandleInertiaRequests.php
public function version(Request $request): ?string
    return vite()->getHash();

// Elsewhere
Inertia::version(fn () => vite()->getHash());

Note that cache-busting is made possible because Vite appends a hash to the bundled files' names.

If you changed Vite's Rollup options manually, you may need to take care of cache-busting yourself.

Server-side rendering

Inertia provides an implementation for server-side rendering, which you can learn about in their documentation.

Using a single development server

The following guide is the simplest way to use server-side rendering with what's already been implemented. However, Vite supports running in middleware mode, so it's possible to create a single server instead of two.

Here is an example implementation.

Creating the server

To use it with Vite, you need to create a new ssr.ts file with almost the same content as main.ts:

import { createSSRApp, h } from 'vue'
import { renderToString } from '@vue/server-renderer'
import { createInertiaApp } from '@inertiajs/inertia-vue3'
import createServer from '@inertiajs/server'

// ...

createServer((page) => createInertiaApp({
  render: renderToString,
  resolve: (name) => resolvePageComponent(name, import.meta.globEager('../views/pages/**/*.vue')),
  setup: ({ app, props, plugin: inertia }) => {
    return createSSRApp({ render: () => h(app, props) })

Configuring Vite

The next thing to do is to add this file to the entrypoints.ssr property of the config/vite.php configuration file.

'entrypoints' => [
    'ssr' => 'resources/scripts/ssr.ts',
    'paths' => 'resources/scripts/main.ts',

Adding package.json scripts

Finally, you may add the relevant scripts to your package.json.

  "scripts": {
    "dev": "vite",
    "dev:ssr": "node public/build/ssr.js",
    "build": "vite build",
    "build:ssr": "vite build --ssr"

You may now run npm run build:ssr && npm run dev:ssr in a separate terminal to start your development server.

Inertia has loaded