Weave Code
Zhylon Auth Laravel Package
zhylon/zhylon-auth
Zhylon Auth is a Laravel authentication package that streamlines user login, registration, and access control. It offers a simple way to add secure auth flows to your applications with minimal configuration. Ideal for projects needing a lightweight, ready-to-use authentication layer.
Zhylon OAuth2 Provider for Laravel Socialite
Frequently asked questions about Zhylon Auth
- How do I install zhylon/zhylon-auth in a Laravel application?
- Install the package with Composer and let Laravel package auto-discovery register its service provider. Publish the configuration file with the vendor publish command so you can review the defaults instead of accepting them blindly. Before installing, confirm the exact package version and its Laravel and PHP constraints in composer.json, because the v1.0 release notes as provided are empty.
- Which Laravel and PHP versions does zhylon/zhylon-auth support?
- The provided overview does not list an explicit Laravel or PHP version matrix. You must verify the illuminate/* and PHP constraints in composer.json and cross-check the README, changelog, and tagged releases before assuming compatibility. Do not rely on the blurb alone, especially for Laravel 10, 11, or 12 on PHP 8.2 and newer.
- Does zhylon-auth replace Laravel Breeze, Jetstream, or Fortify?
- Zhylon Auth is described as a lightweight, Laravel-native authentication layer covering login, registration, logout, guards, and middleware. It is not explicitly positioned as a full starter kit with frontend scaffolding like Breeze or Jetstream. Evaluate whether it provides the UI, routes, and views your project needs, or whether you still need a starter kit or custom controllers.
- How do I configure authentication guards and middleware with zhylon-auth?
- Publish the package configuration and review how it maps guards and middleware into Laravel's existing auth and middleware architecture. Align the published defaults with your application's config/auth.php guards, providers, and route middleware groups. Test the configuration with config caching enabled, because auth packages that read config dynamically can behave differently under cached settings.
- Does zhylon/zhylon-auth include login, registration, and logout flows out of the box?
- Yes, the package overview states that it provides login, registration, and logout flows along with credential validation. You should still inspect the published routes, controllers, and views after installation to confirm they match your application's UX, validation rules, and redirect behavior. Treat the defaults as a starting point and customize them deliberately.
- Does zhylon-auth support password resets and credential validation?
- The package description includes credential validation and password reset support. Confirm how it integrates with Laravel's password broker and mail configuration, since password resets depend on mail delivery and token storage. Verify the reset flow end to end in a non-production environment before relying on it.
- Does zhylon-auth own database tables and migrations, or work with my existing User model?
- The provided context does not confirm whether the package ships publishable migrations and its own models or operates on your existing user model. This matters because packages that own schema couple your application to their migration lifecycle and upgrade cadence. Inspect the package contents and README before installing to determine whether it is a thin library or a persistence-owning auth layer.
- How do I test a Laravel app that uses zhylon-auth?
- Use Laravel's standard testing tools, including RefreshDatabase or in-memory SQLite, and run your existing test suite immediately after installation to surface global side effects. Check whether the package ships its own test suite and CI configuration, which is a useful signal of maintenance quality. Pay attention to middleware, observers, or Blade directives that the provider may register globally.
- Is zhylon-auth safe for production and Laravel Octane?
- At v1.0 the package is young, so validate its stability posture and maintenance activity before putting it on a critical path. For Octane or Swoole, confirm that the package is stateless under long-lived workers and does not hold per-request state in singletons or make synchronous external calls during provider boot. Load-test against production-shaped data and review its query layer for N+1 risks.
- Who maintains zhylon-auth and what is the upgrade or exit plan?
- The available information does not identify a backing organization, support SLA, or license details, so verify these from the repository before adoption. Pin an exact version, assign an internal owner, and record an ADR that documents usage conventions and the removal path. Because the package is small and Composer-distributed, confirm that it is forkable or vendorable if maintenance stops.
Weaver
How can I help you explore Laravel packages today?