Filament Mail Previewer Laravel Package

Product Decisions This Supports

• Roadmap timing for the Laravel 13 upgrade. v0.2.1 explicitly expands the Testbench compatibility range and CI matrix to cover Laravel 13. This removes a blocker from the "upgrade framework version" epic: teams on the Laravel 13 path no longer have to treat mail-preview tooling as an upgrade risk, so the upgrade can be scheduled on its own merits rather than gated by internal tooling work.
• Build vs. buy for transactional email QA. The alternative is building an in-admin mail previewer ourselves. This package is small, purpose-built, and now has boot/plugin/page registration tests — a meaningful signal that the surface we'd depend on is exercised in CI rather than only manually. For a narrow, well-bounded need, "buy" (adopt, contribute upstream) is now the defensible default.
• Scope decisions for the admin panel. The release confirms the plugin API and page registration behavior are intentionally preserved. If we have already specced a Mail Preview section in the Filament admin nav, that spec is unaffected by this release — no rework, no design churn.
• Config ownership and deployment runbook. The fix to how config/mail-previewer.php is registered (with a fallback to the previous config key lookup) means our published config file will actually be honored after upgrade. This is a deploy-time detail worth capturing: it affects whether environment-specific mail preview settings propagate correctly across staging and production.
• Cost avoidance on third-party mail sandboxes. If preview lives in the admin panel, we can reduce reliance on paid email-testing services for day-to-day template review, keeping that spend for deliverability testing rather than visual QA.

When to Consider This Package

Consider it when:

• The application already runs Filament (v3+) as its admin panel; the plugin's value is largely in fitting that surface rather than standing alone.
• The team ships transactional mail (order confirmations, password resets, notifications) and reviewers — design, marketing, support — need to see rendered output without a developer running a local preview.
• You want previews to respect real application data and the real mailable classes, not hand-maintained HTML fixtures.
• You are on or moving to Laravel 13 and want tooling that tracks current framework releases.

Look elsewhere or wait when:

• You are not on Filament — a standalone previewer or a mail-catching service is a better fit.
• You need preview coverage of queued/batched mail pipelines, multi-locale rendering matrices, or visual regression diffing. This is a previewer, not a mail testing platform.
• The package remains pre-1.0 (0.2.x). Version numbers in this range reserve the right to break APIs between minor releases. If your roadmap requires a stability guarantee and vendor support SLAs, this is a stopgap, not a foundation.
• Single-maintainer dependency risk is unacceptable for a critical workflow. Budget for the possibility of forking or absorbing the plugin if the upstream goes quiet.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost Filament plugin that lets non-engineers review transactional emails inside our existing admin panel, removing a recurring developer interruption and reducing dependence on paid email-testing tools for routine visual checks. The new v0.2.1 release keeps it current with Laravel 13, which de-risks our framework upgrade timeline, and fixes a configuration-loading bug that would otherwise have caused environment-specific settings to be ignored after deployment. It is pre-1.0 software from a single maintainer, so we should adopt it for internal tooling with the expectation of occasional maintenance rather than treating it as a long-term platform commitment.

For engineering: v0.2.1 adds Laravel 13 coverage via an expanded Testbench range and CI matrix, adds tests around package boot and plugin/page registration, and fixes config registration so config/mail-previewer.php loads correctly — with a backward-compatible fallback to the prior config key. The Filament plugin API and page registration behavior are explicitly preserved, so this is a safe patch-level upgrade with no expected migration work. Note the config fix may surface previously ignored settings on next deploy; verify published config values in each environment. Still 0.2.x, so pin the version and review changelogs before minor bumps.