Level 15
On the paths you need to be SSRed you can return normal view return view(...) from the controller and laravel will handle rendering these paths on the server and not Inertia
1 like
Mar 8, 2022
10
Level 5
Can Inertia's SSR feature be enabled only for some pages?
I'm trying to decide if I'm going to use Inertia or Livewire for a side project of mine. I'm going to need Server Side Rendering only for a few paths in my app but not all of them and was wondering if Inertia allows for excluding or including only certain Pages to be SSR'ed. I've searched through the docs and the Github issues/discussions and didn't find anything related to this. Has anyone here tried this? Thanks!!
Level 51
@alqahtani How that will work with Inertia, for example if you want the user to load profile page as SPA and also that profile page is public for search engines?
Level 5
@alqahtani But that means I can't use any of my React/Vue components right? I still want some paths to be Inertia, just to not go through the node SSR process.
Level 29
What do you gain by doing this? Why simply not have the whole thing SSRed ?
Level 5
@wingly I'm just curious about the possibility of doing this, not that I really need it to be honest. Having used Next.js in the past where you can choose on a by-page basis what to SSR and what to not I was just wondering if this was possible.
Level 29
@mes Did you get any workaround for this?
Level 1
By setting $__inertiaSsr = null in your blade view you can disable SSR. You can set this depending on the route in your app.blade.php to exclude it from the SSR:
@if(Request::is('app/*'))
@php($__inertiaSsr = null)
@endif
3 likes
Level 5
The listed best answer didn't work for me, but this did:
$__inertiaSsrDispatched = true;
$__inertiaSsrResponse = null;
2 likes
Please or to participate in this conversation.