How to track down source of "Latest compiled component path not found" error

[JonathanLouw]

I'm having a bit of trouble figuring out what could be the cause of the following error:

Latest compiled component path not found

which points to this function in Livewire\Mechanisms\ExtendBlade\DeterministicBladeKeys:

public function generate()
{
    if (! $this->lastPath) {
        throw new \Exception('Latest compiled component path not found.');
    }

    $path = $this->lastPath;
    $count = $this->counter();


    // $key = "lw-[hash of Blade view path]-[current @livewire directive count]"
    return 'lw-' . crc32($this->lastPath) . '-' . $count;
}

Any time I log anything within this function nothing get's logged as if it doesn't even touch this and I don't fully understand how it gets to this function for me to reproduce.

If I understand correctly this is a method used to actually generate the key for the component if it hasn't been created yet. So it uses the lastPath to the view to generate a key and when this hasn't been set it will throw an exception. Livewire seems to intercept blade when it's compiling a view and takes the path to it and sets that as the lastPath. The interception looks like this:

// ExtendBlade.php

app('blade.compiler')->precompiler(function ($value) {
    app(DeterministicBladeKeys::class)->interceptCompile(
        app('blade.compiler'),
    );

    return $value;
});

// DeterministicBladeKeys.php

public function interceptCompile(BladeCompiler $compiler)
{
    $this->lastPath = $compiler->getPath();
}

This is where I'm a bit lost on what's going on, what could possibly cause the interception to fail and not set the lastPath? If something went wrong when rendering the blade view why would it keep executing the logic to generate a key?

Mainly looking for help on how to reproduce this or get a deeper understanding of what's going on so that i can figure out which part of my components are causing this exception.

For context the project i'm working on has been upgraded from v2 to v3 recently and I'm on v3.4.4 of livewire.

[vlChris]

I just randomly stumbled onto this as well. Did you figure out what was causing it?

[JonathanLouw]

From what I understand, this issue may be related to the way blade views are compiled and cached. I've been able to replicate this problem only by deliberately causing a page to break:

1. Run artisan view:clear.
2. Intentionally break the view by adding @php echo $nonExistantVariable; @endphp.
3. Load the page, which will fail due to the undefined variable error.
4. Refresh the page. You'll encounter the same error as before. However, if you check your laravel.log file or Ray, you might notice several "Latest compiled component path not found" errors.

Digging deeper into the compilation engine reveals:

$this->lastCompiled[] = $path;

// If the given view has expired, meaning it has been edited since it was last compiled, we will re-compile the views to evaluate a fresh copy. The compiler is passed the view's path.
if (!isset($this->compiledOrNotExpired[$path]) && $this->compiler->isExpired($path)) {
    $this->compiler->compile($path);
}

// After obtaining the compiled file path, we evaluate the paths with PHP, just like any other template. We also maintain a stack of views that have been rendered to generate the correct exception messages.

try {
    $results = $this->evaluatePath($this->compiler->getCompiledPath($path), $data);
} catch (ViewException $e) {
    if (!str($e->getMessage())->contains(['No such file or directory', 'File does not exist at path'])) {
        throw $e;
    }

    if (!isset($this->compiledOrNotExpired[$path])) {
        throw $e;
    }

    $this->compiler->compile($path);

    $results = $this->evaluatePath($this->compiler->getCompiledPath($path), $data);
}

So, based on the steps above, when the page is refreshed after the first load, it has already compiled a broken view, so it doesn't recompile here:

if (!isset($this->compiledOrNotExpired[$path]) && $this->compiler->isExpired($path)) {
    $this->compiler->compile($path);
}

It appears Livewire attempts to intercept via a pre-compile step to record the compiled path:

app('blade.compiler')->precompiler(function ($value) {
    app(DeterministicBladeKeys::class)->interceptCompile(
        app('blade.compiler'),
    );

    return $value;
});

And in the interceptCompile method:

$this->lastPath = $compiler->getPath();

A cached view, combined with a broken component, means the last path isn't saved by Livewire, leading to this exception. It could be a bug in Livewire regarding how it retrieves the path of the view it's attempting to render, or an issue within a component's view/class being masked by this exception.

Although for me I've only tried reproducing this error on pages with nested Livewire components so that might also be part of what's causing this.

[jozydapozy]

I had this error when running pest-tests.
For me installing the pest-plugin-laravel fixed it.

[binaryfire]

Same. I've got a custom optimze:all command that used to work fine:

<?php

declare(strict_types=1);

namespace Modules\Core\Commands;

use Illuminate\Console\Command;

class OptimizeAllCommand extends Command
{
    protected $signature = 'optimize:all';

    protected $description = 'Cache all the things!';

    public function handle()
    {
        $this->components->info('Caching all the things...');

        collect([
            'config' => fn () => $this->callSilent('config:cache') == 0,
            'events' => fn () => $this->callSilent('event:cache') == 0,
            'filament' => fn () => $this->callSilent('filament:cache-components') == 0,
            'icons' => fn () => $this->callSilent('icons:cache') == 0,
            'routes' => fn () => $this->callSilent('route:cache') == 0,
            'views' => fn () => $this->callSilent('view:cache') == 0,
        ])->each(fn ($task, $description) => $this->components->task($description, $task));

        $this->newLine();
    }
}

Now when it gets to view:cache, I get this:

   Exception

  Latest compiled component path not found.

  at vendor/livewire/livewire/src/Mechanisms/ExtendBlade/DeterministicBladeKeys.php:16
     12▕
     13▕     public function generate()
     14▕     {
     15▕         if (! $this->lastPath) {
  ➜  16▕             throw new \Exception('Latest compiled component path not found.');
     17▕         }
     18▕
     19▕         $path = $this->lastPath;
     20▕         $count = $this->counter();

      +9 vendor frames

  10  [internal]:0
      Illuminate\Foundation\Console\ViewCacheCommand::Illuminate\Foundation\Console\{closure}(Object(Symfony\Component\Finder\SplFileInfo), "/app/vendor/filament/filament/src/../resources/views/components/topbar/index.blade.php")
      +16 vendor frames

  27  modules/core/src/Commands/OptimizeAllCommand.php:25
      Illuminate\Console\Command::callSilent("view:cache")

I've been using this command for almost a year without problems. The odd thing is that running php artisan view:cache directly works fine. Not sure what's going on...

[thijsvdanker]

Looks like it started breaking from version 3.4.0.
I've downgraded to 3.3.5 and don't get the issue anymore.

[binaryfire]

Could anyone make a PR with failing test so Caleb can take a look at it? This one is a bit beyond my skillset unfortunately.

[thijsvdanker]

I've pinpointed it to this commit: f521cfb

[danjdewhurst]

Having this issue too on an Ubuntu server, but cannot replicate locally in Mac OSX. Even running the same post deployment commands like view:cache etc.

EDIT: I seem to get this error sometimes on my server if there is any errors whatsoever in Blade. For example reading properties on null. Fixing those issues stops this error showing, but I'm not sure if that's always the case.

[JonathanLouw]

Yes I've had the same behaviour, if something breaks in a view you get the Latest compiled component path not found error along with the original error.

Are you also nesting livewire components? I seem to be having this issue for pages where a livewire component is used inside another.

[webguy-nz]

Ok, I am having a similar issue to this. I have a component that works fine on my Mac but on Ubuntu I get this error in Ray, while I get undefined variable in the browser. Cannot figure it out at all.

[maverik23]

same issue here.

In my case I call a function all() which I assume is a reserved name.
I changed the name of the function and now I don't have any errors

[octoxan]

I was running into this same issue on version 3.4.8 while following along with a Pest video course at Laracasts.

It turns out the real error was getting lost and I couldn't see it till I downgraded to 3.3.5. That version told me that the Vite manifest was missing. I had never ran npm run build apparently in this project yet, and running that on 3.4.8 made the "Latest compiled component path not found." error stop.

[maverik23]

Okay, I found the problem. When you run artisan view:cache, you get the error "Latest compiled component path not found". This is because when parsing the views and extracting Livewire components, some of the components don't have a defined key().

You can solve this by adding key(Str::random(36)) to each Livewire component.

But how can you track which components don't have a key? You can open the file vendor/livewire/livewire/src/Mechanisms/RenderComponents and add Log::alert($expression); inside the livewire function. This will generate a log with each analyzed component, and the last component without a key will be the one causing the issue.
Execute as many times as necessary to find all components that do not have a key.

You can also use the search feature in VSCode, but it doesn't always find all components.

EDIT:
This is a solution that, although it corrects the problem, is not the best option. use it at your own risk

[joshhanley]

@maverik23 if you can consistently replicate the problem, is there any chance you could share a repo that demonstrates the issue so we can investigate? Ideally we shouldn't need to put keys on every Livewire component so would be good to dig deeper and find out what the root cause is.

[maverik23]

Sorry but I have not been able to replicate the error.
I only know that it was solved by adding KEY in each component.

[dwightwatson]

I've run into this just now, only once upgrading to Laravel 11.x. Occurs on deploy in production when running php artisan optimize but cannot replicate locally on my Mac. I don't use any Livewire components in a loop.

[joshhanley]

@dwightwatson if you can consistently replicate the problem, is there any chance you could share a repo that demonstrates the issue so we can investigate with some detailed instructions on how to replicate it? Thanks!

[naden]

@maverik23 Adding a random key fixed it for me. <livewire:name /> is throwing the error. <livewire:name key="random number" /> works. (code simplified) However this is very hacky and I'm not pushing this into production.

Observation: After running view:clear the first page load renders without exception. When I refresh the page, the above exception occurs. This is reproducible.

[kauffinger]

@maverik23 Adding a random key fixed it for me. <livewire:name /> is throwing the error. <livewire:name key="random number" /> works.

Fixed my deployments by giving static keys to my livewire components (just their component names) - all looped ones have dynamic keys anyways.

[joshhanley]

@naden I've not been able to replicate the issue. If you can consistently replicate the problem, is there any chance you could share a repo that demonstrates the issue so we can investigate with some detailed instructions on how to replicate it? As we would like to get this looked into and fixed. Thanks!

[naden]

@joshhanley I'm compiled a minimalistic snippet for Laravel 10.48.3 and Livewire 3.3.5 also testet with Livewire 4x

Failes:

Blade::compileString("<livewire:dummy />");

Works:

$key = Str::random(7);
Blade::compileString("<livewire:dummy key=\"{$key}\" />");

Content of dummy.blade.php

<div>
    dummy
</div>

[d2inco]

Use the log::alert() method as suggested above, in RenderComponent::livewire(), I'm seeing it in Sanctum(?)'s api.api-token-manager. However, I do not see the problem in a new/bare Laravel 11 project that i just created and then composer required jetstream into (and then jetstream:installed.

The project I encounter the "Latest compiled component path not found"/DeterministicBladeKeys->Generate problem on is one that I converted from Laravel 10 to 11 via Laravel Shift.

So, let me ask this: could this be something related to how Shift does the conversion, possibly injecting something "unusual" into how the pages are iterated over?

[dwightwatson]

I didn't use Shift to upgrade from 10 to 11 - just upgraded the version constraints for Laravel/Sanctum. Perhaps we should be sharing our version numbers to find the pattern here. This discussion is old enough that I presume some people started running into this issue on Laravel 10?

Edit: I've just realised that Laravel 11's artisan optimize command includes view caching, which wasn't enabled in Laravel 10.

[joshhanley]

I managed to work out how to trigger this thanks to @JonathanLouw's steps (I didn't read it properly last time I tried to follow it and missed the nested component step) 🤦‍♂️

I have submitted a PR #8144 with a potential fix.

[d2inco]

Hey, @joshhanley ... I entered the patch in PR #8144 in by hand, and I see no change on this side.... that is, the view:cache is still generating the "Latest compiled component path not found" exception. As well, it is not emitting an Undefined Variable as the PR notes that it should after a view:clear/page-load/page-load (and at this point, I can only best-guess which page (livewire component, really -- all my pages are components in this app) is triggering the exception

[calebporzio]

@d2inco - can you try out this PR and see if it fixes the problem? #8167

[d2inco]

Hey @calebporzio ; preliminarily, at least for me, that appears to work! Even removed all the pre-emptive key="foo"s, and artisan optimize:clear && artisan optimize completes now with no errors thrown.

Thank you!!

[aldoyh]

Hello, thanks for your efforts, I am facing the same issue, and the solution says use this code.. but where do I insert it?

app('blade.compiler')->precompiler(function ($value) {
    // $value is the contents currently being compiled...
    
    app(DeterministicBladeKeys::class)->setCurrentBladeFile(
        app('blade.compiler')->getPath() ?: $value,
    );

    return $value;
});

[joshhanley]

@aldoyh the fix has been merged already. You can install the main branch if you want to test it out, as it hasn't been released it. You shouldn't need the above code.

[dwightwatson]

@joshhanley any idea when we might get a new tagged release?

[joshhanley]

@dwightwatson nope, I've messaged Caleb about it. Hopefully he can do it this week. But if it's being an issue for you, you can install the main branch which has the fixes.