- Can I use msgphp/user-bundle in a Laravel application?
- It is not a drop-in Laravel package. The bundle depends on Symfony bundle registration, DI container compilation, and a msgphp_user configuration tree, which have no direct Laravel equivalent. Running it alongside Laravel means two containers and conflicting service definitions, so the realistic path is to reuse the framework-agnostic msgphp/user domain model and wire it manually in a Laravel ServiceProvider.
- Is msgphp/user-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It sits on msgphp/user (the User, Role, and UserRole domain plus commands and events) and msgphp/domain (message-driven command, query, and event primitives), and it assumes Symfony's runtime and Doctrine ORM. Only the lower domain layer is framework-agnostic PHP and potentially portable to Laravel.
- Does msgphp/user-bundle support Laravel 10 or 11 and PHP 8.1+?
- There is no evidence of Laravel 10 or 11 support. The MsgPHP ecosystem appears dormant and uses PHP 7-era constraints that are likely to conflict with PHP 8.1+ Laravel releases and current Doctrine versions. Run composer why-not against your target Laravel and PHP versions before considering any adoption, and expect to pin or patch at least one transitive dependency.
- How do I install msgphp/user-bundle with Composer?
- Composer installation itself is feasible with composer require msgphp/user-bundle, but bootstrapping it in Laravel is not. The bundle expects Symfony bundle registration and container compilation, so a Laravel app would need to discard the bundle and wire the underlying msgphp/user and msgphp/domain packages manually. Check the last release date and PHP/Doctrine constraints first with composer show msgphp/user-bundle.
- Does msgphp/user-bundle handle login, registration, and password reset, or only the domain model?
- The package description covers registration, login, password reset, and profile handling, with Doctrine-backed user entities and Symfony Security integration. However, much of the authentication surface may be out of scope or delegated to Symfony Security rather than implemented in the bundle itself. Audit the actual code paths before assuming it provides complete, ready-to-use auth flows.
- Can I use Eloquent instead of Doctrine with msgphp/user-bundle?
- Not with the bundle as shipped. Persistence is Doctrine ORM, including bundle wiring and mappings, while Laravel defaults to Eloquent. You could use laravel-doctrine/orm, but that adds a second persistence paradigm; the lower-risk path is to reimplement the User, Role, and UserRole model in Eloquent behind Laravel's existing auth guards.
- Is msgphp/user-bundle maintained and safe for production authentication?
- The adoption signal is near-zero: around 2 stars, 0 dependents, and no evidence of production use, and the MsgPHP ecosystem appears dormant. Taking an unmaintained dependency into the authentication path is a material security risk, especially for password hashing, tokens, verification, and reset flows. The bundle also assumes Symfony's event dispatcher and Doctrine's UnitOfWork, creating hidden coupling that is hard to audit.
- How do I test a Laravel app that integrates msgphp/user-bundle?
- Because the bundle cannot run cleanly inside Laravel, testing usually means testing a manual integration of msgphp/user and msgphp/domain rather than the bundle itself. Write feature tests around your ServiceProvider wiring, command bus adapter, and persistence mappings, and cover auth-sensitive flows such as registration, password reset, and token verification. If you use Doctrine in Laravel, test the mapping and UnitOfWork behaviour separately from your Eloquent-native code.
- How do I reuse msgphp/user's domain model in Laravel without the Symfony bundle?
- Install only msgphp/user and msgphp/domain, which are framework-agnostic PHP, and skip the bundle. Then write a Laravel ServiceProvider, adapt a command bus using Laravel's container or a PSR-11 bus, and map persistence yourself, either through Doctrine or by reimplementing the model in Eloquent. This is effectively a re-implementation project, so weigh the effort against maintained Laravel packages.
- What are the best Laravel alternatives to msgphp/user-bundle?
- Laravel Fortify, Breeze, and Jetstream cover registration, login, password reset, and profile flows with maintained, high-adoption packages. Pair them with spatie/laravel-permission for roles and permissions. Any adoption case for msgphp/user-bundle has to beat these on maintenance, security, and integration effort, and on the evidence available it does not.