Fix component alias resolution for Livewire 4#146
Merged
taylorotwell merged 6 commits intomainfrom Nov 14, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Volt currently depends on Livewire 3 internals to resolve component names.
This PR supports Livewire 4 resolution as well.
I chose to continue the pattern of relying on an internal protected property inside Livewire instead of adding an official affordance for this inside Livewire.
I tested this in the livewire starter kit with both Livewire 3 and Livewire 4 installed and this fixed the errors I was getting in both of them.
Failing tests
All the tests pass locally, however GitHub actions Livewire 12 is failing because of an unrelated error in orchestra/canvas's package discovery.