Weave Code
Email Customization Bundle Laravel Package
rich-id/email-customization-bundle
A Symfony bundle for customizing outgoing emails, with configurable templates, layouts, and styling so applications can brand and tailor transactional messages without duplicating markup across mailers.
At a glance
Frequently asked questions about Email Customization Bundle
- Is rich-id/email-customization-bundle a Laravel package or a Symfony bundle?
- It is described as a Symfony bundle that centralizes email customization for templates, senders, and message content. The available release note is Symfony-centric, so Laravel support may be incidental rather than first-class. Confirm whether it provides Laravel service-provider registration and config publishing before adopting it.
- How do I install rich-id/email-customization-bundle in a Laravel app?
- Install it with Composer using composer require rich-id/email-customization-bundle. Because the package names Symfony 5.4 and PHP 8.0 as its target, run composer why-not against your actual Laravel application to check dependency resolution. Do not rely on ignore-platform-reqs if constraints conflict, because that hides a real compatibility problem.
- Does rich-id/email-customization-bundle support Laravel 11 or Laravel 12?
- There is no evidence in the provided record that Laravel 11 or 12 is supported. The release note targets Symfony 5.4 and PHP 8.0, while Laravel 11 and 12 pin Symfony 7.x. Treat modern Laravel support as unverified until you resolve and test the package in your target application.
- What changed in version 0.2.0 of this email customization bundle?
- The only disclosed change is a compatibility update for Symfony 5.4 and PHP 8.0. No feature, API, or behavior change is described, and no changelog or linked diff is provided. Review the diff between 0.1.x and 0.2.0 for renamed classes, changed config keys, or dropped methods before upgrading.
- Is the Symfony 5.4 and PHP 8.0 reference a minimum floor or a hard pin?
- The record does not state whether the constraint is a floor or a pin. Inspect composer.json and run composer why-not in your application to determine the actual resolution behavior. A floor such as ^5.4 with newer Symfony majors allowed is benign, while a pin to 5.4 will block current Laravel versions.
- Can I customize email templates, senders, and reply-to addresses without editing core code?
- Yes, that is the stated purpose of the bundle. It lets you override templates, configure senders, recipients, and reply-to addresses, and use Twig-powered layouts with shared partials and styling. Service-based customization is intended for dynamic message content, but verify the exact configuration keys in the package docs.
- How should I test email customization with this bundle?
- Pin the exact version 0.2.0 for evaluation, then send through the real mailer path in a scratch application. In Symfony, use the mailer test transport; in Laravel, use the mail fake if integration works. Assert rendered Twig output and headers such as from, reply-to, and recipient values.
- Is it safe to use in production if it targets PHP 8.0 and Symfony 5.4?
- That target matrix is a caution flag because PHP 8.0 reached end of life in November 2023 and Symfony 5.4 is past its support window. A package whose tested path is behind your platform will not receive upstream security fixes along that path. If you adopt it, wrap calls behind an internal adapter, run composer audit, and budget for compatibility maintenance.
- What are alternatives for customizing transactional email templates in Laravel?
- Laravel's built-in Blade mailables, Markdown mailables, and config-driven from and reply-to settings cover most transactional email needs. Publishable Blade views or a Laravel-specific mail theme package can handle shared layouts and branding. Compare those first before adding a Symfony-oriented 0.x dependency.
- Who maintains rich-id/email-customization-bundle and is there a path to 1.0?
- The provided record shows a single visible release event and does not include maintainer, release cadence, or issue-triage data. Pre-1.0 semver means any 0.x minor release may contain breaking changes. Ask upstream for maintainer information, a CI matrix covering Laravel and PHP versions, and a stated path to 1.0 before making an adoption decision.
Weaver
How can I help you explore Laravel packages today?