- Can I use aldhix/breeze-bootstrap-ui with Laravel 11 or PHP 8.1?
- No, this package requires **Laravel 12+** and **PHP 8.2+** due to its dependency on Laravel Breeze v2.3. If you’re on older versions, you’ll need to upgrade first or explore alternatives like custom Blade templates or older Breeze versions.
- Does this package work with Laravel Sanctum or Jetstream?
- This package is designed for **Laravel Breeze** only and assumes its default auth stack. If you’re using Sanctum or Jetstream, you’ll need to manually adapt the Bootstrap views or consider a different package like `laravel/ui` for Bootstrap integration.
- How do I customize the Bootstrap 5 views after installation?
- The package replaces Breeze’s Blade views with Bootstrap versions, stored in `resources/views/vendor/breeze`. Override these files by copying them to `resources/views/vendor/breeze` (or a custom path) and modify them directly. Use Laravel’s view publishing (`php artisan vendor:publish`) if needed.
- Will this package conflict with existing auth middleware or policies?
- The package maintains Breeze’s default auth logic, so it should work seamlessly with Laravel’s built-in middleware (e.g., `auth`, `guest`) and policies. However, if you’ve customized Breeze’s controllers or policies, ensure they align with the package’s assumptions to avoid conflicts.
- Do I need to run migrations after installing aldhix/breeze-bootstrap-ui?
- No, this package **does not add new database tables**. It only replaces Breeze’s Blade views with Bootstrap versions. If you’re using Breeze’s default auth tables (e.g., `users`, `password_resets`), no additional migrations are required.
- Can I use this package without Tailwind CSS?
- Yes, this package is **Tailwind-free** and replaces Breeze’s Tailwind-based views with Bootstrap 5. The installation guide explicitly instructs you to remove Tailwind dependencies (`tailwindcss`, `postcss`, etc.) to avoid conflicts.
- What if I already have custom Breeze views? Will they be overwritten?
- By default, the `breeze-bootstrap-ui:install` command **won’t overwrite existing files** unless you use the `--force` flag. Run the command without `--force` first to preview changes, then manually merge customizations or use `--force` to replace them.
- Is this package compatible with Laravel’s testing tools (Pest/PHPUnit)?
- The package doesn’t include dedicated test utilities, but since it only replaces Blade views, your existing auth tests (e.g., login/registration flows) should continue working. Test edge cases like rate limiting or email verification to ensure compatibility with Laravel’s testing tools.
- What’s the best alternative if I don’t want to use Breeze at all?
- If you’re not using Breeze, consider **`laravel/ui`** for Bootstrap scaffolding or build custom Blade views manually. For API-heavy apps, pair **Sanctum** with a lightweight frontend (e.g., Alpine.js) instead of Breeze’s full-stack auth stack.
- How do I handle production deployment with this package?
- Like Breeze, this package relies on Blade views and Bootstrap CSS/JS. Ensure your production build process includes Bootstrap assets (e.g., via Laravel Mix or Vite). Monitor asset sizes (~500KB+) for high-traffic apps, and optimize with tools like PurgeCSS if needed.