- Is splash/mailjet a Laravel package?
- No. Despite the Laravel/PHP framing, splash/mailjet is a Symfony bundle built as an embedded connector for the Splash Sync middleware platform. It does not ship a Laravel service provider, package auto-discovery, or a native Laravel mail transport. Treat it as Splash Sync infrastructure rather than a drop-in Laravel mailer.
- Can I use splash/mailjet to send email from a Laravel app?
- Not directly. The bundle translates Splash Sync's internal object model into Mailjet API v3 calls, primarily contacts and contact lists, and runs inside the Splash Sync server runtime. It is not a general-purpose Mailjet SDK and does not wire into Laravel's Mail facade or mailer transports. For Laravel email sending, use a dedicated Mailjet transport package or Laravel's own mail configuration instead.
- How do I install splash/mailjet?
- Install it with Composer from the public MIT-licensed repository, then register the Symfony bundle in your Splash Sync host application and supply Mailjet API credentials. There is no documented standalone host app, so installation assumes you already run Splash Sync core and its connector lifecycle. Expect to satisfy Splash core and Symfony version constraints.
- Which Laravel versions does splash/mailjet support?
- None are officially supported. The package targets Symfony applications running Splash Sync, not Laravel, so there is no Laravel version matrix, service provider shim, or package auto-discovery. Any Laravel integration would be custom work at your own risk.
- Which Symfony and PHP versions are supported?
- The available assessment points to Symfony 4, 5, or 6 on PHP 7.4 to 8.x, but verify the composer.json constraints before committing. Because it is an embedded Splash connector, supported versions may be pinned to the Splash Sync core you run. Check compatibility with your platform's PHP and Symfony constraints first.
- What Mailjet objects does it synchronize?
- The connector primarily maps Splash Sync business objects to Mailjet API v3, with contacts and contact lists as the clearest use case. Marketing or transactional objects such as templates, segments, or campaigns are not confirmed in the available documentation. Confirm the exact object mapping and sync direction, whether push, pull, or bidirectional, with the maintainer before relying on it.
- How are Mailjet API keys and rate limits handled?
- Credentials are expected to be supplied through the host Splash Sync configuration, likely via environment variables or the bundle's config schema. The available material does not document retry logic, throttling, or Mailjet rate-limit handling. Inspect the connector code and test failure behavior before production use.
- Is splash/mailjet production-ready and actively maintained?
- Signals are weak: zero stars, zero dependents, a 0.03 score, and no visible test suite or CI badge. It is maintained by a single vendor, Splash, so bus factor and release cadence are legitimate concerns. The MIT license is clean, but licensing is not the same as production validation.
- Do I need Splash Sync to use this package?
- Yes, effectively. The bundle is a node inside the Splash Sync server runtime and depends on Splash core abstractions and Symfony bundle configuration. Standalone adoption means reverse-engineering the Splash connector contract, service tags, and DI container wiring. Adopting Splash Sync just to gain one Mailjet connector is not a pragmatic path.
- What are the alternatives for Mailjet in Laravel?
- For normal Laravel email delivery, use a dedicated Mailjet mail transport package or configure Mailjet SMTP through Laravel's mailer. If you need contact or list synchronization with Mailjet, build a thin API client against Mailjet v3 rather than adopting a Splash Sync bundle. Only choose splash/mailjet if Splash Sync is already a strategic dependency.