Weave Code
Newsletter Laravel Package
nuewire/newsletter
A Laravel newsletter package for managing subscribers, mailing lists, and email campaigns. It provides simple tools to collect signups, organize audiences, and send newsletters from your application, with an emphasis on straightforward integration into existing Laravel projects.
nuewire/newsletter is a Laravel package for managing newsletter subscriptions and delivering email campaigns from your application. It offers a straightforward foundation for collecting subscribers, organizing them into lists, and sending newsletters through Laravel’s mail and queue systems.
- Subscriber and list management
- Email campaign creation and delivery
- Queued sending for better performance
- Integration with Laravel mail and notifications
- Blade-friendly newsletter templates
Frequently asked questions about Newsletter
- How do I install nuewire/newsletter in a Laravel application?
- Install it with composer require nuewire/newsletter, then publish the package assets with php artisan vendor:publish and run php artisan migrate to create the subscriber, list, and campaign tables. You will also need a configured mail provider and a running queue worker before any campaign can be sent. Confirm the exact publish tags and service provider registration in the repository README, because the 1.0.0 release notes only link to a changelog.
- Which Laravel and PHP versions does nuewire/newsletter support?
- The package record does not state its illuminate/* or PHP constraints, so check the require block in composer.json and any CI matrix in the repository before committing. Match those constraints against your application's Laravel and PHP versions, and confirm the published migrations and queued jobs use APIs available in your target release. Laravel major upgrades occasionally change mail and queue contracts, so re-verify after each upgrade.
- Does nuewire/newsletter support double opt-in subscriptions?
- Yes, double opt-in is listed as a core feature: a subscriber is stored in a pending state and only marked confirmed after clicking a signed confirmation link sent by email. Typical implementations also record the opt-in timestamp and source for consent provenance, which you should verify in the published migration columns. Test the flow end to end, including expired or reused confirmation tokens, before relying on it as GDPR evidence.
- How does queued newsletter sending work in this package?
- Campaigns are sent through queued jobs, so a worker must be running and the package must be able to resolve your configured mailer. If it composes with Laravel's Mail facade, pointing it at SES, Postmark, or Mailgun is a matter of config/mail.php rather than a fork; if it ships its own sender abstraction, that changes the integration plan. Verify which applies before you size the work.
- Does it use its own subscribers table or my existing User model?
- This is unconfirmed for 1.0.0: the package most likely publishes its own subscribers, lists, and campaign tables rather than extending your users table, which means you own the schema and every upgrade becomes a migration you reconcile. Decide deliberately whether newsletter subscribers are a separate entity or attached to your User model, and whether you need a polymorphic link. Read the published migrations before running them in a shared database.
- Can I customize the newsletter email templates?
- Customizable templates are a stated feature, and in Laravel terms that usually means publishable Blade views or Markdown mailables you can override in resources/views/vendor. Publish the views, then wrap them in your own layout so branding and unsubscribe footers stay consistent. Keep a plain-text alternative and a working one-click unsubscribe link in every template.
- How are unsubscribes, bounces, and complaints handled?
- Unsubscribes are part of the subscriber lifecycle, so expect a tokenized unsubscribe route plus a suppression flag. Inbound bounces and complaint webhooks are not confirmed for this package; if they are not first-class, you must build listeners for your provider's webhooks and maintain a suppression list yourself. That gap matters for deliverability, because continuing to mail hard-bounced addresses damages your sending domain reputation.
- How can I test newsletter campaigns without emailing real subscribers?
- Use Mail::fake() and Queue::fake() in feature tests to assert that a campaign dispatches the expected mailable and jobs without touching a real transport. For a realistic check, seed a small internal list and send a single campaign through your configured provider before any external send. Always exercise the double opt-in and unsubscribe flows against a test database, since those are the paths most likely to break silently.
- Is nuewire/newsletter production ready and well maintained?
- Treat 1.0.0 as a first stable release with limited evidence: the release notes only link to a changelog, and the nuewire namespace appears to be single-maintainer, so bus factor and long-term maintenance are real risks for a component on your marketing path. Validate the changelog history, open issues, license, and any usage beyond the author before committing. If you adopt it, pin versions and keep integration tests around the send path so a fork or replacement stays cheap.
- What are the alternatives to nuewire/newsletter for Laravel?
- Alternatives include hosted platforms such as Mailchimp or SendGrid Marketing for teams that want deliverability and compliance handled for them, other Laravel newsletter packages, or building directly on Laravel's mail, queue, and scheduler primitives. Choose this package if you want a database-backed subscriber list inside your own application and are prepared to own consent records, suppression lists, and provider webhooks. If you are migrating from a SaaS provider, the import, deduplication, and preserved consent provenance are the hard parts, not the installation.
Weaver
How can I help you explore Laravel packages today?