[fgilio]

The scenario

Right after php artisan view:cache (or optimize), Flux components still compile on the first request that renders them, on every deploy and on every new instance started from that build.

On a fresh app with livewire/flux, run php artisan view:cache, then:

$path = collect(Blade::getAnonymousComponentPaths())->firstWhere('prefix', 'flux')['path'].'/button/index.blade.php';

file_exists(Blade::getCompiledPath($path)); // false

The problem

Flux registers its components through a path with .. in it:

Blade::anonymousComponentPath(__DIR__.'/../stubs/resources/views/flux', 'flux');

Blade names a compiled view after the path the finder returns, and view:cache compiles each file at its real path. So <flux:button> resolves to .../flux/src/../stubs/resources/views/flux/button/index.blade.php, which maps to a different compiled file than the one view:cache wrote, and Blade (or Blaze) compiles it again. On a read-only filesystem, those requests fail.

The solution

Register the same directory without the ..:

Blade::anonymousComponentPath(dirname(__DIR__).'/stubs/resources/views/flux', 'flux');

__DIR__ is already a real path, so this matches what realpath() would return without a filesystem call. On a fresh app, rendering five Flux components right after view:cache compiled 8 Flux views at runtime before this change, and none after.

The general fix is laravel/framework#62005, which runs namespace hints through realpath() like view locations. It only reaches Laravel 13, so this one covers apps on 10, 11 and 12.

FluxProServiceProvider registers its path the same way, so Pro components need the same one-line change.

🤖 Generated with Claude Code

https://claude.ai/code/session_013KFfWQLT7PsmH3zswyjmqv

[fgilio]

FWIW laravel/framework#62005 has just been merged

[ganyicz]

Thanks @fgilio !