- How do I install joggapp/laravel-mail-viewer in a Laravel app?
- Install it with Composer using composer require joggapp/laravel-mail-viewer, then publish and run the package migrations and configuration as described in the README. The package needs database storage for captured mail, so confirm your app's database connection is configured before using the UI.
- Does joggapp/laravel-mail-viewer support Laravel 8?
- Yes. Version 7.0.0 of joggapp/laravel-mail-viewer aligns the package with Laravel 8.x applications. If you are on Laravel 8, update the Composer constraint to v7, refresh the lockfile, run migrations, and execute your test suite. Do not assume Laravel 9 or 10 support without checking the package's exact version matrix.
- Does Laravel Mail Viewer work with Laravel 6 or Laravel 7?
- v7.0.0 drops Laravel 6.x support, so Laravel 6 applications should stay on the prior package major or upgrade the host app first. The release notes do not confirm whether Laravel 7 remains supported, so verify the Composer constraints before adopting v7. Do not infer broader framework compatibility from the Laravel 8 alignment.
- How does Laravel Mail Viewer store sent emails?
- Laravel Mail Viewer stores outgoing mail in your application's database so you can inspect it later from the web UI. That typically includes rendered HTML, plain text, recipients, and attachments, depending on how the package is configured. Because it uses your database, plan for retention, pruning, and sensitive-message handling in shared or production environments.
- Can I resend an email from the Laravel Mail Viewer UI?
- Yes. The package's web UI lets you browse captured emails and resend them. This is useful for debugging transactional flows and retrying failed deliveries during development or controlled support scenarios. Review recipients and environment settings before resending real mail.
- What PHP and PHPUnit versions does laravel-mail-viewer v7 require?
- The v7 release notes indicate alignment with Laravel 8.x and removal of Laravel 6.x support. The context also flags PHPUnit 8 test suites as needing an upgrade before adoption, so teams should confirm the exact PHP and PHPUnit baselines in the package's composer.json and documentation. Do not rely on the release summary alone for the full dependency matrix.
- Is laravel-mail-viewer safe to use in production?
- It can be used in production only with deliberate access controls, since the UI exposes email content, recipients, and attachments. Restrict routes via authentication and authorization, avoid exposing the viewer publicly, and define retention or pruning for stored mail. Validate database growth and sensitive-data policies before enabling it in a live app.
- How can I use Laravel Mail Viewer to test transactional emails?
- Laravel Mail Viewer is useful in testing because it captures actual outgoing mail so you can inspect the rendered HTML, plain text, recipients, and attachments. Use it in staging or local environments to verify transactional templates without relying only on assertions. For automated CI, keep package-dependent smoke tests and confirm your PHPUnit version matches the package baseline.
- Does Laravel Mail Viewer capture attachments and plain text versions?
- The package is designed to let you inspect captured mail content, including rendered HTML, plain text, recipients, and attachments. Actual behavior depends on how your mailables are built and how the package is configured. Test representative emails with attachments to confirm they are stored and displayed as expected.
- Is joggapp/laravel-mail-viewer actively maintained, and what are the alternatives?
- v7.0.0 is primarily a framework-version alignment release for Laravel 8, and the notes do not define a long-term support window or confirm security fixes. Check the repository's release cadence, issue activity, and support policy before standardizing on it. Alternatives include Laravel Telescope's mail watcher for debugging or local SMTP capture tools such as Mailpit, depending on whether you need database-backed resend workflows.