- What is haq/seal used for in Laravel?
- Seal is described as a Laravel package for basic authentication scaffolding using Blade, Bootstrap, and Livewire. It helps you add ready-made auth views and components to a Laravel app instead of building login, registration, and related screens from scratch. Confirm the exact features in the README before adopting it.
- How do I install haq/seal with Composer?
- Install it in a Laravel application with composer require haq/seal, then follow the package README for any service provider, publishing, migration, or asset steps. Run the command from your project root and commit the resulting composer.json and lock file changes. If the package requires Livewire, make sure Livewire is installed and configured first.
- Which Laravel versions does haq/seal support?
- The provided overview does not list supported Laravel versions, so check the package's composer.json constraints and README before installing. Pay attention to its illuminate/support and livewire/livewire requirements, because those determine compatibility. If you are on an older or newer Laravel release, test in a branch first.
- What frontend stack does Seal use for authentication scaffolding?
- Seal uses Blade templates, Bootstrap styling, and Livewire components for its authentication scaffolding. That makes it a fit for Laravel projects already using Bootstrap and Livewire rather than Tailwind-based starter kits. You can customize the markup, but the default look and behavior assume that stack.
- Does Seal replace Laravel Breeze, Jetstream, or Fortify?
- Seal is described as basic authentication scaffolding, so it overlaps with starter kits like Breeze and Jetstream but may not include their full feature set. Fortify is a backend authentication implementation, while Seal focuses on Blade, Bootstrap, and Livewire scaffolding. Compare features such as password reset, email verification, profile management, and two-factor support before choosing.
- How do I customize Seal's login and registration views?
- Because Seal uses Blade and Livewire, customization normally means publishing its views and Livewire components and then editing the templates. Check the README for vendor:publish tags and any config file that controls routes or redirects. Keep your changes in version control so package updates do not overwrite them.
- Can I use Seal with Tailwind CSS instead of Bootstrap?
- Seal's default scaffolding is built with Bootstrap, so switching to Tailwind means replacing or rewriting the Blade markup and styles. You can do that in your own views, but it is not the default setup and may require adjusting Livewire component templates. If you want a Tailwind-first starter kit, Laravel Breeze is the more direct option.
- Does haq/seal encrypt or protect application data?
- The package overview describes Seal as authentication scaffolding, while the short blurb mentions sealing utilities for protecting application data. Those are different concerns, so verify the actual API and README before using it for encryption or data protection. For application data encryption, Laravel's built-in Crypt facade or a dedicated security package is a safer starting point.
- How should I test authentication flows built with Seal?
- Use Laravel's HTTP testing helpers to assert that login, registration, and logout routes behave correctly, and use Livewire::test for any Livewire auth components. Run tests against a fresh test database and cover validation errors, redirects, and authenticated versus guest access. Also test the published views after customization.
- Is haq/seal production ready and actively maintained?
- The provided context does not include release history, issue activity, or a TPM assessment, so check Packagist, GitHub releases, open issues, and the last commit date before using it in production. Pin a tested version in composer.json and review the package code for your security requirements. For critical auth, favor well-maintained Laravel starter kits or official packages unless Seal meets your audit needs.