- Is igdr/messanger-bundle a Laravel package?
- No. It is a Symfony bundle, which you can tell from the Bundle suffix and the igdr vendor namespace, and it ships no Laravel ServiceProvider or Facade. Laravel's package discovery will not auto-register it, so it cannot be treated as a drop-in Composer dependency in a Laravel application.
- Will Laravel package discovery register igdr/messanger-bundle automatically?
- It will not. Auto-discovery depends on an extra.laravel block in composer.json pointing at a ServiceProvider and optional Facades, and a Symfony bundle provides neither. Wiring it up would require manual registration or a custom bridge, and the repository publishes no Laravel integration surface.
- Which Laravel and PHP versions does igdr/messanger-bundle support?
- That cannot be confirmed from the available information, so read the composer.json constraints yourself. Symfony bundles of this vintage commonly pin symfony/* requirements that conflict with the framework versions Laravel's ecosystem expects, producing Composer resolution dead ends. Check the constraints before you attempt a require.
- How do I install igdr/messanger-bundle in a Laravel project?
- Composer require will download the code, but nothing will boot it. Symfony bundles are registered in a Symfony Kernel's bundles array, which Laravel does not have. Running it means booting Symfony components inside a Laravel service provider, a high-friction path the package does not document or support.
- Is igdr/messanger-bundle safe to use in production?
- Treat it as unvetted third-party code. The repository shows 0 stars, 0 dependents, and no evidence of active maintenance, security patching, or PHP version bumps. Read the source in full and assign an internal owner plus a patch SLA before any production exposure.
- Does igdr/messanger-bundle replace Laravel's queue, events, or bus?
- No, and it should not be framed that way. Symfony Messenger's transports, middleware stack, and envelope semantics do not map one-to-one onto Illuminate queue jobs, ShouldQueue events, or the Bus pipeline. Laravel already provides queued jobs, chained buses, failed-job tables, and Horizon supervision out of the box.
- Can I run Symfony Messenger alongside Laravel's queue in the same app?
- Technically yes, but you would be operating two parallel messaging stacks in one process. That risks duplicate service resolution, conflicting autoloaders, and two competing event loops. If your estate is mixed Laravel and Symfony, share a broker such as Redis, SQS, or RabbitMQ instead of importing Symfony abstractions into Laravel.
- What does igdr/messanger-bundle add over vanilla Symfony Messenger?
- That is the key question and it requires source inspection to answer. Look at the transport list, the middleware, the DI extension, and whether it pins Symfony 3 or 4 era APIs. If it adds nothing substantive beyond core Messenger, the bundle is better mined for design patterns than installed.
- How should I test or evaluate this bundle before adopting it?
- Run a one to two day spike that reads the source and documents its transport and middleware model. There is no test badge or release cadence to lean on, so your own reading is the only validation available. Specifically verify idempotency, dead-lettering, and poison-message quarantine, the failure modes that actually matter for messaging.
- What is the Laravel-native alternative for private messaging between users?
- Build on Laravel's own primitives: queued jobs, events and listeners, a database or broker queue connection, and Horizon for supervision. If you need an adapter, implement the Illuminate\Contracts\Queue\Queue contract backed by the same broker rather than importing the bundle. If adoption is unavoidable because a Symfony service depends on it, isolate it behind an anti-corruption layer so Laravel code never touches Symfony abstractions directly.