Weave Code
Articlelist Widget Laravel Package
friendsofvictoire/articlelist-widget
A Laravel package that provides a configurable article list widget for rendering and displaying article collections in your application.
At a glance
Frequently asked questions about Articlelist Widget
- Is friendsofvictoire/articlelist-widget actually a Laravel package?
- No. Despite the Composer name and the Laravel-focused description, the repository is a Symfony bundle that registers through the Symfony kernel and DI container and depends on Victoire CMS, a Symfony 2/3-era CMS. There is no service provider, no facade, and no compatible extension point in Laravel. The artifact is a CMS admin widget, essentially a form type plus a Twig template for selecting and ordering articles in an editorial back office. Treat the Laravel framing as a naming mismatch, not a feature.
- Can I install this package with Composer in a Laravel 10 or 11 application?
- In practice, no. Composer resolution will almost certainly fail against any modern PHP 8.1+ or Symfony 5/6/7 constraint set, and forcing it in means pinning the whole application back to end-of-life runtime versions. Even as a dev-only dependency it expands your audit surface for no functional gain. Run composer why-not against your project to capture the concrete conflict before writing it off.
- Which PHP and Symfony versions does the bundle support?
- The last release was 2019-04-09, and its Victoire CMS dependency is Symfony 2/3-era, which effectively implies Symfony 3.4 or lower and PHP 7.x. There is no PHP 8 compatibility work, no security response process, and no active maintainer. Assume it is incompatible with PHP 8.x and Symfony 5+ unless your own composer why-not output proves otherwise for your exact constraint set.
- How do I render an article list widget in a Blade view with this package?
- You cannot, because it ships no Blade directive or component tag and renders through Twig inside a Symfony CMS admin. The equivalent in Laravel is straightforward: an Eloquent query with explicit ordering and limit, passed to a Blade partial or a small Livewire component. That gives you the same configurable list with full control over the item markup.
- What is the best alternative for a configurable article list in Laravel?
- Build it natively. A form request or simple filter class plus an Eloquent query handles ordering, limits, and filtering, and a Blade partial or Livewire component handles the item views. If you need it in an admin panel, a Nova or Filament field covers the editorial use case. This is a UI feature, not a library decision, so there is no package worth adopting for it.
- How much effort is it to reimplement this widget myself?
- Roughly one to two developer-days including tests. The scope is a query for article selection, an ordering column, and a Blade, Livewire, Nova, or Filament presentation component with an overridable item template. That is almost certainly cheaper than carrying an abandoned dependency indefinitely, and you own the code from day one rather than inheriting a decade-old Symfony codebase.
- Is the package maintained, and is it safe to use in production?
- It is abandoned: last release in April 2019, zero stars, zero dependents, and no downstream validation. There is no maintainer to ship security fixes, and the transitive dependency tree reaches into Victoire and Symfony 2-era packages that carry their own unpatched advisories. Adopting it transfers full ownership of unfamiliar legacy code to your team with no offsetting benefit.
- How do I prove the package is incompatible before rejecting it?
- Run composer why-not friendsofvictoire/articlelist-widget in the target project and capture the output. That documents the exact PHP or Symfony constraint conflict, so the rejection is evidenced rather than asserted in review. Keep the output with your dependency evaluation notes in case someone revisits the decision later.
- Does this bundle integrate with Laravel Nova or Filament?
- No. There is no Laravel integration of any kind, so nothing here plugs into Nova or Filament. The concept does transfer cleanly though: a Nova field or Filament form component that selects articles and persists an ordering column reproduces the whole idea. Read the bundle as a reference implementation for field semantics and template structure, not as an installable dependency.
- We still run a legacy Victoire CMS site. Should we adopt this bundle there?
- Only if that system already depends on Victoire and you accept that it pins you to Symfony 3.4-era runtimes. Even then, isolate it behind an internal API boundary so the modern application never links against the bundle directly. If the legacy system is on a modernization roadmap, this bundle is a blocker rather than an asset, and you should plan the native replacement instead.
Weaver
How can I help you explore Laravel packages today?