- What is kompo/auth and what does it actually do?
- Kompo Auth is a Laravel authentication package that plugs into the Kompo component suite. It ships ready-made login, registration, and password reset flows built from customizable Kompo UI components, so you do not have to hand-build those screens. The goal is a fast, consistent auth setup across applications that already use Kompo.
- How do I install kompo/auth with Composer?
- Install it with composer require kompo/auth inside your Laravel project. After that, follow the package README for any service provider registration, configuration publishing, asset publishing, or migration steps it requires. Because it belongs to the Kompo suite, check the README for the recommended setup order relative to the other Kompo packages you use.
- Does kompo/auth work in a plain Laravel app without Kompo components?
- Kompo Auth is designed around the Kompo component suite, so its views and UI pieces assume Kompo is present. A plain Laravel app without Kompo would likely need the suite installed first, or you would need to replace the provided components with your own Blade views. Review the README requirements before adopting it in a non-Kompo codebase.
- Which Laravel versions does kompo/auth support?
- The authoritative answer is the require section of the package's composer.json plus the compatibility notes in the README. Check those before installing into an existing application, especially on older Laravel releases or PHP versions. If your Laravel version is not listed, install it in a scratch project first to confirm resolution succeeds.
- How do I customize the login and registration forms?
- The forms are delivered as Kompo components, so customization happens through the component classes and their field definitions rather than editing raw Blade templates. Typical changes include adding or removing fields, adjusting validation rules, and changing layout or styling on the component. Publish any package views or config first if you need to override defaults, and keep overrides in your app so upgrades stay simple.
- Does kompo/auth handle password reset emails and the related routes?
- The package advertises ready-made password reset flows, meaning the request form, the reset form, and the underlying Laravel password broker integration are covered. Email delivery itself still relies on your Laravel mail configuration and the password reset notification. Confirm the exact routes and notification behavior in the README or package source for your version.
- Can I use kompo/auth together with Breeze, Jetstream, or Fortify?
- Running two auth scaffolds at once usually causes duplicate routes, conflicting controllers, and confusing view resolution. Pick one system for the routes and guards you expose, and remove or disable the other's auth routes before enabling Kompo Auth. If you only want Fortify's backend features, you can keep it for logic and use Kompo Auth purely for the UI layer, but verify route conflicts carefully.
- How do I write tests for authentication flows built with kompo/auth?
- Test them like any Laravel auth flow: use RefreshDatabase, create a user with a known password, post credentials to the login route, and assert the user is authenticated with Laravel's assertAuthenticated helper. For registration and password reset, assert the user record and the queued or sent notification rather than the rendered markup where possible. Also check the package's own test suite in the repository for the route names and request payloads it expects.
- Is kompo/auth actively maintained and safe for production?
- Check the GitHub repository for recent commits, tagged releases, open issues, and whether the composer.json constraints track current Laravel versions. Because it is part of the Kompo suite, releases typically follow the suite's cadence rather than a standalone schedule. Before production use, review the source of the auth controllers and verify your own rate limiting, throttling, and session configuration.
- What are the alternatives to kompo/auth?
- The main alternatives are Laravel Breeze, Jetstream, Fortify, and the older Laravel UI package, plus writing your own controllers with Laravel's built-in Auth facade and password broker. Breeze and Jetstream are first-party and Blade, Livewire, or Inertia based, while Kompo Auth is the natural choice only if your front end is already built with Kompo components. If you need fine control over every auth screen, custom controllers often end up simpler than adapting any scaffold.