Should `livewire-components.php` be tracked?

[fgilio]

This is not a bug nor a feature request. Should livewire-components.php be tracked in git?

Just had an error while deploying a project because Livewire couldn't find a component. I had a gut feeling that it was something in livewire-components.php and indeed it was. The file was outdated and that component was missing.
I tried running php artisan livewire:discover but it failed, I guess it was a file permissions error (using Laravel Forge).

Ended up fixing it by telling git to track the file and deploying again.

EDIT 2019-09-14:
The permissions errors when running php artisan livewire:discover where 100% on my side. So I guess nobody has to worry about that.

[intrepidws]

Or maybe we should be adding php artisan livewire:discover to our deploy scripts?

[fgilio]

Yes, it could be. Imo a solution that doesn't require the user to do anything would be preferable, but maybe it's just not possible.
I can later dig into the server to see why php artisan livewire:discover failed.

[intrepidws]

Interesting that it failed. I had the same exact issue as you but was able to run php artisan livewire:discover just fine. I'm using Laravel Forge as well.

[ninthspace]

I've had this too, usually when I switch between development machines and then pull down new content from a repo. To work around, I've updated composer.json:

    "post-autoload-dump": [
      "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
      "@php artisan package:discover --ansi",
      "@php artisan livewire:discover"
    ],

[tillkruss]

@ninthspace: That seems to be a reasonable solution to accelerate the first request and to cache the components on ephemeral filesystems.

LivewireComponentsFinder::getManifest() will build and save the livewire-components.php if it doesn't exist.

[fgilio]

* The permissions errors when running php artisan livewire:discover where 100% on my side. So I guess nobody has to worry about that 😅

[lancepioch]

@fgilio Can the issue be closed?

[intellow]

I will submit a PR later today that will automatically regenerate the manifest if Livewire cannot find a component. This will eliminate the ComponentNotFoundException from being thrown unless it is valid (the component does not exist or is in the wrong namespace).

Of course, this still wouldn't help if the regeneration of the manifest file is blocked by server permissions. 😄

[fgilio]

@fgilio Can the issue be closed?

I thinks so, yep

I will submit a PR later today that will automatically regenerate the manifest if Livewire cannot find a component...

Amazing!

[kundakaps]

i have tried all the solutions here but still getting

A Livewire component was not found
You might have forgotten to discover your Livewire components. You can discover your Livewire components using php artisan livewire:discover.
Pressing the button below will try to discover your Livewire components.