White screen / Silent failure when using Blaze::optimize() in AppServiceProvider

[vnshah]

After enabling Blaze::optimize() and targeting the components directory, the application fails to render. The browser displays a blank white page with no error messages, and the Blaze profiler stays stuck on a "Loading..." state.

Steps To Reproduce

1. Install livewire/blaze and livewire/flux (compatible versions).
2. Add the following to the boot method of AppServiceProvider.php:

   public function boot(): void{
   \Livewire\Blaze\Blaze::optimize()->in(resource_path('views/components'));
   }
3. Run php artisan view:clear in the terminal.
4. Refresh the application in the browser.

• The page results in a completely white screen (WSOD).
• No errors are logged in laravel.log or displayed on the screen.
• The Blaze profiler bar appears but remains in a "loading" state indefinitely.
• Removing the Blaze::optimize() line resolves the issue immediately.

[ganyicz]

Hi @vnshah

Can you please provide code snippet of the Blade view you're rendering and its compiled file?

[mrstu84]

I am seeing something very similar with my installation too. Here are more details, and a possible cause, for me use case.

It appears that Laravel Debugbar exhausts the PHP memory limit (128MB) during response rendering. The fatal error occurs in "php-debugbar/JavascriptRenderer.php:1319."

Environment
PHP 8.4.15
Laravel 12.53.0
Livewire 4.2.0
livewire/blaze 1.0.2
livewire/flux 2.12.2
barryvdh/laravel-debugbar 3.16.5
php-debugbar/php-debugbar 2.2.6

OS: macOS (Darwin 24.6.0), served via Laravel Herd

Steps to Reproduce

1. Install livewire/blaze in a project using livewire/flux
2. Enable Blaze optimisation for a directory of anonymous components: Blaze::optimize()->in(resource_path('views/components/ui'));
3. Ensure debugbar is enabled (default in local environment)
4. Load a page that renders several Blaze-compiled components (e.g. a listing page with repeated anonymous components in a loop)

Behaviour

Fatal error - memory limit exhausted:
Allowed memory size of 134217728 bytes exhausted (tried to allocate 31457312 bytes) at vendor/php-debugbar/php-debugbar/src/DebugBar/JavascriptRenderer.php:1319

Debugging Attempted

• Disabling the views collector via DEBUGBAR_COLLECTORS_VIEWS=false in .env - did not resolve the issue
• Adding paths to exclude_paths in the published config/debugbar.php (e.g. vendor/livewire/flux, vendor/livewire/flux-pro) - did not resolve the issue
• Disabling debugbar entirely via DEBUGBAR_ENABLED=false - resolves the issue, implying debugbar is the source of the memory consumption

Workaround

Disable debugbar entirely when using Blaze:
DEBUGBAR_ENABLED=false

[ganyicz]

@mrstu84 can you please create a separate issue for this? I don't believe it is related as the original author doesn't mention Laravel Debugbar at all.

[mrstu84]

@ganyicz No problem. I think my issue has subsequently covered here #84 I'll add a comment there to give you context. #

[himanshumehru]

I have this issue with white screen as well when using blaze optimize in app service provider. I'm using flux pro but also have additional components that are not flux.

[joshhanley]

@himanshumehru can you please provide the views and components you are trying to load that create the white screen? Is it more than just one page?

[himanshumehru]

Yea, it kills the entire site. I'm using livewire starter kit with flux pro. Loading some page components from livewire config with resource paths. 🙏

…

On Fri, Feb 27, 2026 at 5:50 PM Josh Hanley ***@***.***> wrote: *joshhanley* left a comment (livewire/blaze#82) <#82 (comment)> @himanshumehru <https://github.com/himanshumehru> can you please provide the views and components you are trying to load that create the white screen? Is it more than just one page? — Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUEOEM5H5RVHRBFFFLT7OT4ODX7JAVCNFSM6AAAAACWBTSM4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNZWGA2DIMJXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[himanshumehru]

basic optimizations work fine with flux out of the box but when I try to use the optimize in app service provider, i see the white screen of death for all routes. Not sure how I can help short of making my private repo public or sharing it with you?

[himanshumehru]

@joshhanley Here is some code: <?php

namespace App\Providers;

use Illuminate\Support\ServiceProvider;
use Livewire\Blaze\Blaze;

class AppServiceProvider extends ServiceProvider
{
/**
* Register any application services.
*/
public function register(): void
{
//
}

/**
 * Bootstrap any application services.
 */
public function boot(): void
{

    $this->configureBlaze();
}

/**
 * Configure Blaze optimization for Blade components.
 *
 * Strategy:
 * - Flux UI components are auto-optimized by Blaze (no config needed)
 * - Livewire components (⚡ prefix) are class-based and excluded automatically
 * - Layout components use function compile only (contain global state: auth, request, @can)
 * - Static shared components can use fold: true for maximum performance
 */
protected function configureBlaze(): void
{
    // Enable debug profiler in local/staging for performance analysis
    if (app()->environment('local', 'staging')) {
        Blaze::debug();
    }

    Blaze::optimize()
        // Layout components - function compile only (uses auth(), request(), @can, @csrf)
        ->in(resource_path('views/components/layouts'))

        // Settings layout - function compile only (uses request() for active state)
        ->in(resource_path('views/components/settings'))

        // Help components - function compile
        ->in(resource_path('views/components/help'))

        // Attachments - function compile (stateless display components)
        ->in(resource_path('views/components/attachments'));

    // Note: Components with @blaze directives added directly:
    // - views/components/shared/timeline.blade.php (fold: true)
    // - views/components/shared/page-header.blade.php (fold: true)
    // - views/components/shared/back-button.blade.php (compile only - uses session())
}

}

And the livewire config:

'component_namespaces' => [
    'layouts' => resource_path('views/components/layouts'),
    'contacts' => resource_path('views/components/contacts'),
    'tickets' => resource_path('views/components/tickets'),
    'settings' => resource_path('views/components/settings'),
    'emails' => resource_path('views/components/emails'),
    'texts' => resource_path('views/components/texts'),
    'calls' => resource_path('views/components/calls'),
],

[himanshumehru]

@joshhanley Not sure if this is helpful, but I checked developer tools and I see this warning when configureBlaze() is not commented out in my app service provider: This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “”. Learn more

[ganyicz]

@himanshumehru

Looking at your service provider it looks like you're also optimizing Livewire components - those can't be rendered using Blaze and would explain the white screen. Instead of optimizing the entire components folder, only add @blaze to non-livewire components.

I understand this is not ideal as you want to be able to optimize the entire components folder however that's where Livewire components now also live. I'll see if we can automatically detect this or add Blaze support in Livewire components.

[himanshumehru]

@ganyicz Thanks your advice fixed the issue and helped me understand how things work better. Thank YOU!

[ganyicz]

Hi @vnshah,

I'm going to close this now as I wasn't able to reproduce the issue but feel free to reply here in case the issue persists.

As mentioned above the problem might be that livewire components are getting optimized. If you're optimizing the entire resources/views/components consider only adding @blaze to non-livewire components.