Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Table Widget

Table Widget Laravel Package

friendsofvictoire/table-widget

friendsofvictoire/table-widget is a Laravel package for rendering reusable, configurable data tables in Blade views. Define columns and rows once, then reuse the widget across admin pages and dashboards for consistent table output.

View on GitHub
Deep Wiki
Context7

Victoire DCMS Table widget

Frequently asked questions about Table Widget
Is friendsofvictoire/table-widget a Laravel package?
No. Despite being listed in Laravel package contexts, it ships as WidgetTableBundle, a Symfony bundle that relies on Symfony bundle registration, DI extensions, tagged services, and likely Twig. Laravel's service provider and Blade architecture are adjacent but not compatible, so adoption requires a rewrite rather than a composer require.
Can I install friendsofvictoire/table-widget in a Laravel app with composer require?
Composer may resolve it, but you will not get a working Laravel integration. There is no Laravel service provider, Blade directive, or Laravel-facing configuration—the bundle expects Symfony's kernel and bundle registration. On modern PHP 8.x and current Laravel versions, dependency constraints are also likely to block or break installation.
Does friendsofvictoire/table-widget support Laravel 10 or 11?
No. Its last release is from 2016-10-06 and targets the PHP 5.6/7.0 and Symfony 2.x/3.x era. It will almost certainly fail on PHP 8.x and cannot satisfy modern Laravel version constraints. No maintained bridge exists.
Is friendsofvictoire/table-widget abandoned?
Yes, by all available signals. The last release was October 2016, roughly nine years dormant, with 1 star, 0 dependents, and no evidence of production use. There is no active maintainer to fix bugs, review security, or issue patches.
What should I use instead of friendsofvictoire/table-widget for Laravel tables?
Use Laravel-native options: Filament tables for admin panels, Livewire for interactive tables, Inertia with a JavaScript data grid, or a thin custom Blade component. These are maintained, tested against current Laravel/PHP versions, and cover filtering, sorting, and pagination. Pick based on whether you need server-rendered Blade output or an interactive grid.
Is friendsofvictoire/table-widget safe to use in production?
Not recommended. It is unmaintained and unaudited, and table widgets render user-influenced data into HTML, which makes stored XSS a real concern. With no maintainer, there is no path to a CVE or security patch. Treat the security surface as unvetted.
Can friendsofvictoire/table-widget render Eloquent query builders or collections?
Not directly in Laravel. The package is Symfony/Twig-oriented; any Eloquent-friendly behavior would have to be extracted from the bundle and re-hosted behind a Laravel service provider and Blade views. That is a reimplementation effort, not integration. Confirm the actual domain logic in source before committing.
How do I render friendsofvictoire/table-widget tables in Blade?
You cannot without a rewrite. The bundle is built around Symfony/Twig rendering, so there is no Blade directive or Laravel component to drop into a view. The realistic path is to copy the pattern—column definitions, formatting, visibility—and build a native Blade component or use Filament/Livewire.
What license does friendsofvictoire/table-widget use, and can I copy code from it?
License and provenance are unclear from the available signals. Verify the license before copying any code, not just before requiring the package. If you extract logic, confirm the license permits relicensing within your codebase.
Should I fork friendsofvictoire/table-widget or rewrite it natively?
Treat it as a reference implementation, not a dependency. Read the source to identify genuinely non-trivial behavior—column definition API, formatting rules, pagination model—and decide build versus lift. If the logic is thin, as is likely for a table widget, build native; if not, port algorithms and not Symfony wiring, and assign an owner for the fork.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core