Laravel Livewire: Livewire\Exceptions\ComponentNotFoundException: Unable to find component: [admin.users]
Livewire can't resolve a component alias to a class — wrong name, namespace or discovery.
Unable to find component: [admin.users]Livewire\Exceptions\ComponentNotFoundException: Unable to find componentUnable to find component LivewireLivewire component not foundNo component found for [x] Meaning
Component names map to classes in App\Livewire (v3) or App\Http\Livewire (v2): admin.users → App\Livewire\Admin\Users. Check class name/namespace, file location, and that you didn't upgrade versions without moving components. Clear caches and run composer dump-autoload.
Common causes
- Class not in the expected namespace/path
- Livewire v2→v3 namespace change
- Typo or case mismatch (Linux)
- Component not registered for packages
- Cached views/classes stale
⚡ Quick fix
- Place the class at
app/Livewire/Admin/Users.php php artisan livewire:make Admin/Usersto generate correctlycomposer dump-autoload && php artisan view:clear
Detailed fix by platform
Laravel
php artisan livewire:make Admin/Users
How to diagnose
- Name — Alias → class?
- Version — v2 or v3 paths?
- Case — Matches disk?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 403 This action is unauthorized Laravel: Illuminate\Auth\Access\AuthorizationException: This action is unauthorized.
- Attempt to read property "x" on null Laravel/PHP 8: ErrorException: Attempt to read property "name" on null
- Class "App\Models\X" not found Laravel: Error: Class "App\Models\Post" not found
Most viewed in Laravel
- MassAssignmentException Laravel: Illuminate\Database\Eloquent\MassAssignmentException: Add [x] to fillable property to allow mass assignment
- The GET method is not supported for route Laravel: The GET method is not supported for route x. Supported methods: POST (MethodNotAllowedHttpException)
- Route [login] not defined Laravel: Symfony\Component\Routing\Exception\RouteNotFoundException: Route [login] not defined
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026