Merged
Conversation
This reverts commit 20baaaf.
Clarify the usage of Blaze components and rendering.
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
2 participants
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.
Blaze 1.0 is here!
A reliable, drop-in optimization for your Laravel app that eliminates most of the overhead from anonymous Blade component rendering, with additional strategies available for even greater gains.
Function compilation
The new default strategy compiles anonymous components into plain PHP functions, skipping the standard rendering pipeline and eliminating ~90% of overhead.
More reliable folding
Blaze now detects when folding would produce incorrect output and automatically falls back to function compilation, so you still get a significant performance improvement.
Blade profiler
Blaze now includes a fully-featured profiler for analyzing the rendering performance of your views. See exactly how long each component takes to render, identify bottlenecks, and measure the impact of your optimizations.
Flux users
If you're using Flux, we've already updated all Flux components to be maximally optimized. Just update to the latest version and you're good to go.
Breaking changes
If you're upgrading from the 1.0-beta,
@blazeno longer enables folding or memoization by default — it enables function compilation only. You'll need to opt in explicitly with@blaze(fold: true)or viaBlaze::optimize(). See the full upgrade guide for details.Learn more
For full documentation on all optimization strategies, configuration options, and limitations, see the README.