[3.x] Migrate Blade components to inline syntax#850
Merged
pascalbaljet merged 3 commits into3.xfrom Mar 25, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
<x-inertia::app>and<x-inertia::head>Blade components were returning dynamic HTML strings from their render closures. Laravel treats these as inline Blade templates and writes a compiled cache file tostorage/framework/viewsfor each unique string.This PR switches to static inline Blade templates with public properties for the dynamic data. The template string is always identical, so it compiles and caches exactly once. The SSR content flows through variables instead of being embedded in the template itself.