- How do I install pxlrbt/laravel-notification-preview in a Laravel app?
- Install it with Composer using composer require pxlrbt/laravel-notification-preview. Laravel package discovery should register the service provider, but check the README for any publish or configuration steps. Install it in local or development environments first and confirm your PHP version satisfies the package constraints.
- Which Laravel and PHP versions does laravel-notification-preview support?
- The supplied release note confirms v1.1.0 adds Laravel 13 support, but it does not include a full support matrix. Check the package's composer.json for exact PHP and Laravel constraints, and confirm whether Laravel 10, 11, and 12 are still supported before upgrading.
- Does laravel-notification-preview send real notifications or only render previews?
- Its stated purpose is to let you browse, preview, and test-send notifications and mailables, but the package blurb emphasizes previewing without sending. Treat real delivery as opt-in and configure mail to a safe local driver. Confirm the exact test-send behavior in the package docs before using it against real recipients.
- How do I preview a Laravel notification's mail content as HTML and text?
- The package renders mail notifications and mailables as both HTML and text so you can inspect content, formatting, and styling. Open the preview UI, select the notification or mailable, and review both renderings before shipping. This helps catch layout issues that only appear in one mail format.
- Can I preview database and broadcast notification payloads with this package?
- For non-mail channels, the package shows the notification payload rather than a channel-specific rendered view. That lets you inspect the data that would be sent to database, broadcast, and similar channels. Use it to verify payload structure and content during development.
- Is there a UI for browsing all notifications and mailables in my app?
- Yes, the package provides a local preview UI for browsing notifications and mailables in your Laravel app. It is intended for development-time inspection rather than end-user delivery. Check the package docs for the route, middleware, and authorization setup.
- How do I test-send a Laravel notification to verify formatting and recipients?
- The package description advertises test-send support for notifications and mailables. Use a local mail driver or log transport when testing so you do not deliver to real users, and verify recipient handling in the preview UI. Check the package documentation for the exact test-send command or UI action.
- What are the alternatives to laravel-notification-preview for previewing Laravel mail?
- For automated tests, Laravel's Notification::fake and Mail::fake let you assert notifications without rendering a UI. For visual mail checks, local mail catchers such as Mailpit or Mailhog are common. This package differentiates by browsing and rendering notifications and mailables inside a Laravel preview UI.
- Is pxlrbt/laravel-notification-preview safe for production and how is it maintained?
- It is a development and debugging aid, so avoid exposing its preview routes in production or protect them with authentication and environment checks. The compatibility release is assessed as low-to-moderate risk, but you should verify composer constraints, PHP version, and CI coverage before rollout. Pin the version and review the changelog for future Laravel releases.
- How do I upgrade to v1.1.0 for Laravel 13 and what should I check?
- Treat v1.1.0 as a Laravel 13 compatibility release: inspect the changelog and composer.json diff, update the package in a sandbox or CI branch, and run your full test suite. Confirm whether dependency constraints were widened or narrowed and whether Laravel 10, 11, and 12 remain supported. Define a rollback step before promoting to production.