- Is baks-dev/auth-email fully compatible with Laravel 11, or will I need manual fixes?
- The package officially supports Laravel 10/11 due to PHP 8.4+ requirements, but Symfony 7.0+ dependencies may introduce minor friction with Laravel’s Symfony components (e.g., HttpFoundation). Test thoroughly, especially if using custom request handling or Artisan commands. No Laravel 11-specific optimizations are documented in v7.4.9.
- How do I install this package in a Laravel project without breaking existing auth (e.g., Laravel Breeze/Jetstream)?
- Run `composer require baks-dev/auth-email`, then override Laravel’s default guard in `AuthServiceProvider` to extend email auth. Use `php artisan baks:assets:install` for assets, but manually merge Doctrine migrations with Eloquent if needed. Avoid conflicts by isolating the package in a separate service provider.
- Does this package support Eloquent models, or am I forced to use Doctrine ORM?
- The package defaults to Doctrine ORM for migrations, but you can manually adapt models to Eloquent by translating Doctrine entities. No hybrid mode or Eloquent adapter is officially documented. Test database interactions thoroughly, as Doctrine’s query builder differs from Eloquent’s.
- What are the risks of using Symfony 7.0+ components in a Laravel project?
- Laravel relies on Symfony 6.x components, so Symfony 7.0+ could introduce deprecations (e.g., HttpFoundation changes) that break request handling or console commands. Focus on testing request objects, Artisan wrappers, and any custom Symfony bindings. Monitor Laravel’s Symfony component updates for compatibility patches.
- Can I use this package alongside Laravel’s built-in auth (e.g., for hybrid email/social login)?
- Yes, but you’ll need to extend Laravel’s `AuthManager` to support the custom email guard. The package doesn’t natively integrate with Laravel’s social auth (e.g., Jetstream), so manual bridging is required. Consider whether the overhead justifies the Symfony dependency if you only need email auth.
- How do I handle conflicts with baks-dev/core (e.g., version mismatches or Laravel incompatibilities)?
- Use Laravel’s `replace` config in `composer.json` to override `baks-dev/core` if conflicts arise, but this may not fully resolve Symfony integration issues. Alternatively, fork the package and remove Symfony-specific bindings. Test in a fresh Laravel 11 project first to identify risks early.
- Are there performance benchmarks comparing Doctrine vs. Eloquent for auth in Laravel?
- No official benchmarks exist, but Doctrine’s query builder is generally slower than Eloquent for simple auth operations. If performance is critical, consider using Eloquent models with manually translated Doctrine migrations. Profile your auth flow with Laravel Debugbar to compare latency.
- Does this package include frontend assets (e.g., Blade views, Tailwind CSS) for email auth?
- The package provides installable assets via `php artisan baks:assets:install`, but they’re Symfony-centric and may require Laravel-specific adjustments (e.g., Blade directives, Tailwind config). Review the `resources/views` output and extend or override as needed for Laravel’s frontend stack.
- How do I run the included PHPUnit tests for auth-email in a Laravel project?
- Execute `php bin/phpunit --group=auth-email` from the package root. Tests assume Symfony’s environment, so mock Laravel’s dependencies (e.g., `Illuminate/Foundation`) or run tests in a standalone Symfony context. For Laravel integration tests, extend the group with custom test cases using Laravel’s testing helpers.
- What alternatives to baks-dev/auth-email exist for Laravel email auth with better Laravel integration?
- Laravel’s native auth (with custom email validation) or packages like `spatie/laravel-permission` (for role-based email auth) offer tighter Laravel integration. For Symfony-free solutions, consider `laravel/breeze` (email auth) or `laravel/jetstream` (advanced auth). Evaluate whether the package’s Doctrine migrations justify the Symfony dependency overhead.