- Does kassoulet/swiftmarkbundle work with Laravel?
- No. SwiftmarkBundle is a Symfony bundle built on Bundle subclasses, DependencyInjection extensions and YAML/XML service definitions, and it ships no Laravel service provider, facade or package auto-discovery. Composer can install it, but Laravel's container will not wire any of it. The practical route in Laravel is the framework's own Markdown mailables.
- Is SwiftmarkBundle compatible with Laravel 9, 10 or 11?
- No. The bundle is built on Swift Mailer, which reached end of life in November 2021 and was dropped from Laravel 9 and later. Even if you lifted the renderer out, you would re-register it yourself, which removes any reason to take the dependency. Use league/commonmark instead, which Laravel already runs under the hood.
- What is the Laravel equivalent of SwiftmarkBundle?
- Laravel has shipped first-class Markdown mailables since 5.7: create a Mailable, point it at a Markdown view, and Laravel renders an HTML part plus an automatic plain-text alternative using league/commonmark. That delivers the same one-template, two-parts behaviour with a maintained, security-patched parser. No extra package is required.
- How do I install SwiftmarkBundle?
- You would normally run composer require kassoulet/swiftmarkbundle, then register the bundle in a Symfony application's bundles.php or kernel and add its configuration. There is no Laravel installation path because there is no service provider. Its Swift Mailer dependency makes it unusable on Laravel 9+ regardless.
- Does SwiftmarkBundle generate a plain-text version of emails?
- Yes, per its documentation it renders one Markdown source into both an HTML part and a matching plain-text fallback. That dual-output behaviour is the main capability worth copying if you rebuild the feature. Laravel Markdown mailables produce the same HTML and text pair automatically.
- Is Swift Mailer still supported and safe to use?
- No. Swift Mailer was deprecated and reached end of life in November 2021, so it receives no security fixes. It was dropped from Laravel 9+ and Symfony 6 in favour of Symfony Mailer and Laravel's own mailer. Running it today means owning an unsupported transport layer.
- What Markdown parser does SwiftmarkBundle use?
- The bundle advertises a pluggable Markdown parser with configurable renderer options, but the documentation provided does not pin a specific library or version. Check its composer.json for league/commonmark or an older parser and confirm that parser is still maintained. In practice league/commonmark is the maintained choice and is what Laravel uses.
- Is SwiftmarkBundle actively maintained?
- There is very little signal: zero stars, zero dependents, no referenced CI matrix and a single maintainer. That means no evidence the code runs in any environment, let alone yours, and no realistic CVE-response capability. Treat it as a reference implementation rather than a production dependency.
- How do I migrate away from SwiftmarkBundle to Laravel?
- First run a dependency scan to confirm nothing in your codebase requires it, which is likely given zero known dependents. Then write down the behaviour you actually need: Markdown dialect, enabled extensions such as tables and footnotes, how the plain-text part is generated, and how the HTML is themed. Rebuild that on league/commonmark behind Laravel's Markdown mailable and lock it down with golden-file tests over a corpus of real templates, typically one to two engineer-days.
- What should I use instead of SwiftmarkBundle for Markdown emails?
- In Laravel, use Markdown mailables with league/commonmark; in Symfony, use Symfony Mailer with a league/commonmark-backed template renderer. Both are maintained, receive security patches, and live inside the frameworks you already run. Rebuilding the renderer yourself is roughly 100 to 200 lines, which is cheaper than adopting an unmaintained bundle.