README

Deprecated: This package is no longer maintained. Inertia.js v2 now includes native support for this functionality through "Once Props". Please use the official implementation instead: https://inertiajs.com/docs/v2/data-props/once-props

Optimize Inertia.js applications by loading static data only during the first page load.

A Laravel package that improves performance by caching static data on the client side, reducing payload sizes and processing time for subsequent requests.

Table of Contents

1. Introduction
2. Installation
3. Usage
4. Manually Refreshing Static Props
5. Adding Static Props to Component Renders
6. How It Works
7. License

Introduction

Inertia Static Props optimizes your Inertia.js application by loading static data only once during the initial page load. After that, static props are cached in the frontend and injected into the page props on every subsequent visit.

By using static props, you can significantly reduce the payload size and processing time for subsequent requests, leading to improved performance.

Installation

The package consists of two parts: a Laravel backend package and a frontend adapter.

Backend

Install the package via Composer:

composer require jessegall/inertia-static-props

The package will auto-register its service provider if you're using Laravel's package auto-discovery.

Otherwise, you can manually register the service provider:

\JesseGall\InertiaStaticProps\ServiceProvider::class

Frontend

1. Install the frontend adapter via npm:

npm i inertia-static-props

1. Set up the plugin in your Inertia application:

// Import the plugin import {inertiaStaticPropsPlugin} from "inertia-static-props"; createInertiaApp({ setup({el, App, props, plugin}) { createApp({render: () => h(App, props)}) .use(plugin) // Add other plugins... .use(inertiaStaticPropsPlugin) // Register the static props plugin .mount(el); }, });

Usage

You can share static props from anywhere in your application.

The most common place is in your HandleInertiaRequests middleware, but this is not required:

use JesseGall\InertiaStaticProps\StaticProp; use Inertia\Inertia; class HandleInertiaRequests extends Middleware { public function share(Request $request): array { return [ ...parent::share($request), // Using a StaticProp instance 'translations' => new StaticProp(fn() => $this->resolveTranslations()), // Using the Inertia helper 'enums' => Inertia::static(fn() => $this->resolveEnums()), ]; } }

The shared static props will always be available in the page props.

// In your page components <script setup>  const props = defineProps([  'translations',  'enums'  ]) </script> // Using the page helper <script setup>  import {usePage} from "@inertiajs/vue3";   const page = usePage();  page.props.translations;  page.props.enums; </script> // Or in the template <template> <div> {{ $page.props.translations }} {{ $page.props.enums }} </div> </template>

Thats it! The static props will be cached in the frontend and injected into the page props on every subsequent visit.

Manually Refreshing Static Props

Sometimes you need to refresh static props after certain actions, like changing the users locale, or when the user permissions change.

class LocaleController extends Controller { public function update(...) { // Something that requires a static prop refresh ... // Reload all static props Inertia::reloadStaticProps(); } }

Adding Static Props to Component Renders

Though, not recommended, it is possible to include static props when rendering components.

return Inertia::render('Component', [ 'regularProp' => 'value', 'staticPropExample' => new StaticProp(fn() => 'static value'), ]);

Warning

Static props are only sent to the client during the initial page load.

When your controller is accessed after the initial page load, you'll need to reload the static props to ensure the static props are sent to the client.

return Inertia::render(...)->withStaticProps(); // Add static props to the response

How It Works

Behind the scenes, the package:

1. Identifies props wrapped in StaticProp during the initial page load
2. Evaluates these props and sends them to the client
3. Caches them in the frontend (browser)
4. On subsequent requests, these props will NOT be resolved on the server and are removed from the response.
5. The client-side adapter injects the cached props back into the page props before Inertia processes them, creating a seamless experience as if the server had sent them.

This results in smaller payloads and reduced server processing time for subsequent requests.

License

MIT