[2.x] Add livewire component paths to default refresh paths for livewire stack #1081
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.
This is dependent on merging and tagging of:
[0.3.x] Addapp/View/Components/**
to default refresh paths vite-plugin#55so the tests are currently failing, however this has been tested locally.
This PR additionally watches
app/Http/Livewire/**
in the Livewire stack, as "inline" components contain all their view logic there. When files there change, the browser will perform a full page refresh.Test script...
Put the following in your
welcome.blade.php
Then put the following in your Livewire component...
You should not be able to edit the Livewire component and see the browser refresh and show the new content.