- Is mpp/message-bundle compatible with Laravel?
- No. mpp/message-bundle is a Symfony bundle, not a Laravel package: it ships a Symfony Bundle class, a DependencyInjection extension, and service definitions loaded by the Symfony kernel, with no Laravel ServiceProvider or container bindings. There is no supported mechanism to register a Symfony bundle in a Laravel application. On a Laravel stack you should treat it as source material and port the messaging design rather than install it as a dependency.
- How do I install mpp/message-bundle?
- Install it with Composer using composer require mpp/message-bundle, then register and configure the bundle using Symfony's normal bundle registration flow, such as bundles.php or your kernel configuration. Because it is a Symfony bundle, installation assumes a Symfony application rather than a generic PHP or Laravel project.
- Which Symfony versions does mpp/message-bundle support?
- Version 4.0.0 was released as a compatibility update for Symfony 7. The major version bump for that compatibility chore suggests the package tracks Symfony major releases rather than promising long-term support across older Symfony lines. Check the release tags and composer constraints if you need a specific Symfony version.
- What features does mpp/message-bundle provide for private messaging?
- The bundle provides reusable message entities, conversation threading, and services for sending, storing, and retrieving user-to-user messages in inbox-style conversations. It also includes bundle-style service and configuration registration plus an extensible structure for custom message workflows. The goal is to avoid rebuilding common message model, repository, and service wiring from scratch.
- Can I use mpp/message-bundle with Laravel Mail or Laravel Notifications?
- Not directly. The bundle is wired for Symfony services and likely depends on Symfony contracts such as MailerInterface or container parameters, while Laravel uses Mail, Notifications, Queue, and its own service container. To use the design in Laravel you would need to reimplement the delivery and integration layer against Laravel's subsystems, or extract any framework-agnostic core first.
- Is mpp/message-bundle actively maintained?
- The maintenance signal is thin: the repository has zero stars, zero dependents, and only about five pull requests over its life. The v4.0.0 release merged a one-line Symfony 7 compatibility change, which shows the maintainer is still attentive and will accept outside contributions, but it is not evidence of a long-term support commitment. Bus factor is likely one, and there is no issue history or security advisory trail to review.
- How much work is it to extract mpp/message-bundle for a Laravel app?
- It depends on how much of the bundle is framework-agnostic core versus Symfony glue. If the delivery orchestration sits behind PSR-3 logging, PSR-18 HTTP, PSR-14 events, and Symfony Messenger's transport abstraction, extraction could be a two-to-five day spike; if the logic is entangled with Doctrine entities, Symfony's MailerInterface, or compile-time container parameters, the cost rises materially. Read the source end to end before committing to an estimate.
- What are alternatives to mpp/message-bundle for Laravel messaging?
- For Laravel applications, start with native capabilities: Laravel Notifications for delivery, Mail for email, database notifications for persistence, and queues for background processing. For threaded inbox-style messaging you can model conversations and messages with your own Eloquent models and services, or evaluate actively maintained Laravel messaging packages. The key criteria are Laravel version support, test coverage, and a clear security and maintenance history.
- How should I test a Laravel port of mpp/message-bundle?
- Write characterization tests against the original bundle's behavior where possible, especially around conversation threading, sending, storing, and retrieving messages. In Laravel, use Notification::fake, Queue::fake, and database transactions to isolate delivery and persistence, and add explicit tests for tenant, queue-name, and provider assumptions that may be undocumented. Then keep those tests as regression coverage for your own implementation.
- Is mpp/message-bundle safe for production use?
- The MIT license and small surface area are positives, and you can vendor and own the code without legal friction. However, there is no external validation, no dependents, no issue history, and no security advisory trail, and the bundle was extracted from one company's infrastructure, so it may carry hidden assumptions about queues, tenancy, or mail providers. On Symfony, audit and own it before production; on Laravel, do not install it and instead port the design.