Weave Code
Core Laravel Package
phplist/core
Core library for phpList, the open-source newsletter and email marketing system. Provides shared domain logic, models, and services for managing subscribers, lists, campaigns, and message sending in PHP applications.
This module is the core of phpList 4. Join discussion at the community forum: https://discuss.phplist.org/
Frequently asked questions about Core
- What is phplist/core and can I use it in a Laravel application?
- phplist/core is the foundational PHP domain library behind phpList, covering subscribers, lists, attributes, campaigns, and batched queue processing. It is not a Laravel-native package, so you should treat it as an embedded newsletter bounded context behind an adapter rather than a drop-in Laravel component. A Laravel integration is feasible only with custom service providers, configuration, database wiring, and a controller or API layer. Verify its runtime assumptions before committing.
- Does phplist/core support Laravel 10 or Laravel 11 out of the box?
- There is no evidence of first-class Laravel 10 or 11 support, service providers, config publishing, or Eloquent integration in phplist/core. It is the domain core of phpList 4 and may expect Symfony/Doctrine-style runtime pieces or the phpList application context. Expect to pin dependencies and build an anti-corruption adapter. Run a Composer install check against your exact Laravel and PHP versions early.
- How do I install phplist/core with Composer in a Laravel project?
- You would install it with composer require phplist/core, but the real work is resolving dependency constraints and bootstrapping its services. Start in an isolated proof-of-concept app or container, not directly inside a production Laravel codebase. Confirm that it installs standalone and exposes stable public APIs before adding adapter code. If Composer conflicts appear, isolate the package behind a separate worker or service.
- What PHP version and dependencies does phplist/core require?
- The README excerpt does not list PHP version or dependency constraints, so inspect the package composer.json and lock file directly. Because the last release was in March 2021, expect possible PHP-version drift and stale transitive dependencies. Validate the dependency graph against your Laravel version and database driver in a clean environment. Pin versions or containerize the package if constraints conflict.
- Does phplist/core ship database migrations and models for Laravel?
- phplist/core provides database-backed persistence for phpList domain concepts, but it is not documented as shipping Laravel migrations or Eloquent models. You must verify whether it includes schema migrations, upgrade paths, and a stable persistence API. In Laravel, avoid exposing its models directly to application code; map your users and lists through an adapter. Plan for schema ownership and migration testing explicitly.
- How does phplist/core handle campaign queues and batched email sending?
- The package includes campaign queueing and batched message processing as part of phpList's proven mailing engine. It is not a Laravel queue integration, so you will likely need to wire workers, cron or scheduler assumptions, SMTP transport, throttling, and bounce handling yourself. Confirm queue semantics and throughput at your required scale. A pilot with limited sending volume is essential.
- Is phplist/core's AGPL-3.0 license compatible with a closed-source Laravel SaaS?
- phplist/core is AGPL-3.0, a strong copyleft license that can create obligations for modifications and network use. That may be a blocker for closed-source or commercial distribution, so legal review is required before architectural commitment. Track any modifications and understand whether your integration triggers source-disclosure duties. Do not assume Laravel's MIT licensing carries over to this dependency.
- Is phplist/core actively maintained and safe for production?
- The last release was 2021-03-02, stars are low, and upstream activity appears limited, so production use carries maintenance and security-patching risk. Community-only support and sparse documentation increase delivery risk. Budget for a fork or internal maintainer role, or avoid strategic dependence. Run a dependency and security audit before relying on it.
- What are alternatives to phplist/core for Laravel newsletter and list management?
- If you need Laravel-native conventions, consider building on Laravel notifications and mailables, or evaluating maintained newsletter services and packages with explicit Laravel support. phpList-style list and campaign semantics may still justify phplist/core in an isolated service, but only after a proof of concept. Compare licensing, maintenance cadence, queue behavior, and bounce handling. Falling back to a maintained service is reasonable if the PoC shows tight coupling.
- How should I test a phplist/core integration before committing in Laravel?
- Run a time-boxed proof of concept that installs the package via Composer, boots its core services, creates a list, subscriber, and campaign, enqueues a test message, and verifies schema behavior. Test in an isolated environment with your target PHP, database, and Laravel versions. Confirm public API stability, migration path, queue worker assumptions, and SMTP transport. Only then define the adapter boundary and pilot with limited sending volume.
Weaver
How can I help you explore Laravel packages today?