Weave Code
Extra Laravel Package
stampie/extra
stampie/extra extends Stampie, the PHP library for sending email through provider APIs, with additional adapters, helpers, and convenience classes. It simplifies adding extra mail-service integrations and common email-sending functionality to PHP applications.
Event-based plugin for stampie/stampie
Frequently asked questions about Extra
- What is stampie/extra used for?
- stampie/extra is an event-based plugin that extends the Stampie PHP email library with additional provider adapters, helpers, and convenience classes. It is intended for applications already using Stampie to send email through provider APIs. It is not a Laravel-first package and does not replace Laravel Mail.
- Is stampie/extra compatible with Laravel?
- Technically it can be installed via Composer and wrapped in a custom Laravel mail transport or service-container binding, but that is not idiomatic. Compatibility depends on whether its older PHP, Symfony, and PSR dependency constraints resolve against your Laravel version. Expect friction, and run a short compatibility spike before committing.
- How do I install stampie/extra with Composer?
- In a throwaway branch, run composer require stampie/extra and let Composer resolve its transitive dependencies against your target Laravel version. Because the package is archived, pin the resolved version and commit the lock file if you proceed. Do not assume the install will remain conflict-free across future Laravel or PHP upgrades.
- Can stampie/extra be used as a Laravel mail driver?
- Not natively. You would need to isolate it behind a custom MailTransport or provider-adapter interface and keep Laravel Mail as the primary abstraction. That keeps application code from depending on Stampie types. Treat it as a narrow internal adapter, not a general Laravel mail driver.
- Is stampie/extra still maintained?
- No active upstream maintenance should be assumed. The package is archived, has low adoption signals, and shows no release since May 2022. If you adopt it, your team effectively owns maintenance, compatibility checks, and security review.
- What are the production risks of using stampie/extra?
- The main risks are missing upstream bug fixes and security patches, dependency conflicts with current Laravel or PHP versions, and duplicated configuration, retry, observability, and testing paths. Provider API changes may require reading old source and reproducing behavior manually. Use it only for a small, isolated, non-critical mail flow, and plan an exit path from day one.
- Does stampie/extra work with Laravel queues and mail events?
- It does not integrate with Laravel queueing, mail events, or testing hooks out of the box. Those behaviors live in Laravel Mail and would need to be preserved around your adapter. You should add contract tests for send, failure, retry, and provider response handling.
- How does stampie/extra compare with Laravel Mail and Symfony Mailer?
- Laravel Mail provides a mature abstraction with first-party drivers, queueing, events, and testing hooks, while Symfony Mailer is actively maintained and commonly used underneath. stampie/extra is an extension for the older Stampie mailer and adds a parallel transport layer. For most Laravel applications, native Laravel Mail or a maintained provider SDK is the better default.
- How should I test a stampie/extra integration?
- Build a narrow proof of concept behind an adapter and add contract tests for successful send, failure, retry, and provider response handling. Verify dependency resolution against your target Laravel version and deployment PHP runtime. Keep the integration isolated so it can be removed without touching application code.
- What if I need a provider adapter that Laravel Mail does not support?
- First check the provider's official SDK and whether a small custom Symfony transport or Laravel MailTransport can cover the missing behavior. If stampie/extra is the only source of that capability, wrap it in one internal adapter and document a fork or exit plan. Because upstream is archived, forking means treating it as a maintained internal library.
Weaver
How can I help you explore Laravel packages today?