- Can I use baks-dev/auth-email with Laravel’s Eloquent ORM instead of Doctrine?
- No, the package is hard-coupled to Doctrine ORM and lacks Eloquent support. You’d need to manually rewrite migrations, models, and queries or fork the package, which introduces significant technical debt. Laravel’s built-in auth systems (e.g., Breeze/Jetstream) are better suited for Eloquent projects.
- What Laravel versions are officially supported by this package?
- The package requires PHP 8.4+, aligning with Laravel 10/11. However, it depends on Symfony 7.0+, which may conflict with Laravel’s Symfony components (e.g., symfony/console v6.x). Laravel 12+ could face further compatibility risks due to Symfony 7.0+ deprecations.
- How do I resolve dependency conflicts with baks-dev/core in a Laravel project?
- Use Laravel’s `replace` config in `composer.json` to isolate `baks-dev/core`, but this may not fully resolve Symfony 7.0+ conflicts. Alternatively, wrap the package’s console commands (e.g., `baks:assets:install`) in custom Laravel Artisan commands. Test thoroughly in a staging environment before production.
- Does this package support social logins or OAuth like Laravel Breeze/Jetstream?
- No, this package enforces email-only authentication. If you need social logins, OAuth, or multi-factor auth, Laravel’s official packages (Breeze, Jetstream, or Sanctum) are more flexible and maintainable. This package’s monolithic design makes extensions difficult.
- How do I integrate the package’s Blade templates into Laravel’s frontend?
- The package includes Symfony-templated views (e.g., `resources/views/auth-email/`). Override these in Laravel’s `resources/views/` directory, but expect styling and logic mismatches. For a seamless experience, consider building custom Blade templates from scratch or using Laravel’s built-in auth scaffolding.
- Are there performance benchmarks comparing Doctrine vs. Eloquent for auth flows?
- No official benchmarks exist for this package. Doctrine ORM typically adds overhead compared to Eloquent’s lightweight query builder, especially in high-traffic Laravel apps. If performance is critical, Eloquent-based auth systems (like Breeze) are recommended.
- How do I run the package’s PHPUnit tests in a Laravel project?
- Run `php artisan test --group=auth-email` if the package registers its test suite with Laravel’s test runner. Otherwise, use the provided command: `php bin/phpunit --group=auth-email`. Note: Tests are Symfony-centric and may not cover Laravel-specific edge cases like HTTP middleware or Blade rendering.
- What’s the fallback plan if Symfony 7.0+ introduces breaking changes?
- Pin Symfony components to v6.x in `composer.json` under `conflict` or `replace` directives, but this may break package functionality. Monitor the package’s GitHub for updates or consider migrating to Laravel’s native auth systems. The package’s stagnant release cycle (last update in 2026) adds long-term risk.
- Can I use baks-dev/captcha with Laravel’s built-in CSRF protection?
- Potential conflicts may arise due to differing middleware stacks. Test CAPTCHA integration in a staging environment, ensuring it doesn’t interfere with Laravel’s `VerifyCsrfToken` middleware. The package’s Russian-only documentation may also complicate troubleshooting.
- Why should I choose this package over Laravel Breeze/Jetstream for email auth?
- This package offers Doctrine migrations and a Symfony-centric stack, but Laravel Breeze/Jetstream provide superior Laravel integration, Blade templates, API support, and active maintenance. Unless you’re already using Doctrine or Symfony 7.0+, the customization effort and technical debt outweigh the benefits.