What about whole Inertia.js pages inside a Filament panel? 👀 I've been experimenting with this too! React / Vue / Svelte, with Filament navigation, actions, etc. around it. Not a "coming soon" this time though… this needs changes to Inertia itself

These support many Inertia features: pass props from your PHP page, submit forms, return validation errors, load deferred props, etc. I've been testing React, Vue and Svelte, with and without SSR, and with Filament's SPA mode too. Also alongside an existing Inertia frontend.

The tricky part is letting Livewire still handle navigation, while Inertia handles the content. I've opened a PR for Inertia to make that possible. The Inertia team might not like the idea, or how it's implemented, they're completely entitled to decline! But pretty cool to see.

@inertiajs can we remove livewire entirely ?

@inertiajs No, we have many features built on Livewire that we would not be able to replicate with the same developer experience

@inertiajs yeah it must be very complex 😂, i try built from scratch before AI comes, here is the repo its completly different, but the idea is the same

@inertiajs This unlocks so many possibilities

@filamentphp @inertiajs .. but why?

@filamentphp @inertiajs Some people prefer building with Inertia rather than Livewire or have more experience with it. This would let them use that workflow for custom pages, while still getting Filament's Livewire-powered resources, navigation, actions, etc. without building a whole admin from scratch.

@inertiajs I guess @pascalbaljet would love to collaborate 👀

@inertiajs Depending on the complexity of your filament apps, there are complex pages that requires using react/vue for maximum interactivity. Paired with the recent boost in the speed of filament, this is a blessing for those who need it. I have been using Mingle for this purpose!

@inertiajs awesome, would love to see it getting implemented

@filamentphp @inertiajs Wow you’re a genius! I like inertia because it splits the complexity in a good way: Server does routing, permissions and DB. Client renders the UI and reuses it Livewire renders UI on the server which feels out of place (is “spa mode” different?)

@inertiajs 🔥🔥

@inertiajs Yes please!

@filamentphp @inertiajs Hi Dan, did you try mingle?

@inertiajs This is a dream come through!!! Go all out bro.

@inertiajs This gives me hope, I'm currently in the process of porting my entire dashboard to inertia/react, i'm 90% done but this gives me hope to stick with filament a few weeks longer

@filamentphp @inertiajs I can see the value for filament users but I really hope I never have to work on a project that has so much package specific context: livewire, filament, inertiajs + Frankenstein mode (this) haha. Livewire alone felt like too much to me the one time I worked with it

@filamentphp @inertiajs This is actually minimising the package specific context for a portion of users, and not increasing it for anyone else. Inertia users can use Inertia everywhere instead of switching to Livewire just inside Filament, and Livewire users continue not using Inertia.

@inertiajs nice idea btw... but how you create and add styles to vue/react components? won't be easy to create a separate library a web components lib for that?.. (for example like polaris web components, like shopify does)

@inertiajs This is a compelling bridge between Filament’s server-driven ergonomics and Inertia’s client-side flexibility. The key design win is keeping navigation and actions coherent while letting each page choose the right rendering model.

@inertiajs It will be foolish IMHO for the Laravel Inertia team to reject this.