- What does joy/voyager-datatable do?
- It is a Voyager module that integrates Yajra DataTables into Laravel Voyager BREAD listings. Instead of Voyager's basic table output, your admin screens get searchable, sortable, and paginated data tables. It is meant for projects that already use Voyager as their admin panel and want richer tabular views without leaving the familiar BREAD workflow.
- How do I install joy/voyager-datatable in a Laravel application?
- Install it with Composer alongside Voyager, then publish the package config and assets. Next you configure the BREAD entries for the tables you want to enhance and override the relevant Voyager views so the DataTables scripts and markup are included. The process is manual and incremental, so validate one read-only listing in staging before rolling it out across all BREAD views.
- Does joy/voyager-datatable support Laravel 10 and Laravel 11?
- Compatibility with Laravel 10 and 11 is not formally verified. The last release was in February 2024, so it most likely targeted Laravel 9 or 10 with Voyager 1.x. Run a proof of concept in a staging environment, watch for deprecation warnings and dependency conflicts, and pin exact versions in Composer.
- Does it work with PHP 8.2 and newer PHP versions?
- PHP 8.2 and above compatibility is unconfirmed by the maintainer, and there is no CI matrix or test suite to prove it. Check the composer.json platform constraints before installing and run the package under your target PHP version in staging first. If you hit type or deprecation errors, expect to patch the code yourself.
- Which Voyager version is required for joy/voyager-datatable?
- The package is built around Voyager 1.x and extends its BREAD views, models, and view overriding conventions. It will not work as a standalone table component outside of Voyager. Confirm the exact Voyager constraint in composer.json and verify that your Voyager installation is itself actively maintained before adopting this module.
- Is joy/voyager-datatable actively maintained?
- No, maintenance is minimal. The project has roughly 13 stars, zero dependents, no visible CI or test suite, and no releases since February 2024, with an effective bus factor of one. For production use you should assume ownership of bug fixes, security patches, and Laravel compatibility updates, likely by forking the repository privately.
- Can I use joy/voyager-datatable with Filament, Nova, or Backpack instead of Voyager?
- No. The package is tightly coupled to Voyager's BREAD architecture and its view layer, so it is not usable with Filament, Nova, Backpack, or API-only Laravel projects. If you are not already on Voyager, the architectural mismatch is significant and you should use a panel-native table solution instead.
- What are the alternatives to joy/voyager-datatable?
- The most direct alternative is installing yajra/laravel-datatables yourself and wiring it into your own Blade views or admin panel, which gives you a maintained dependency without the Voyager coupling. You can also write a small custom DataTables integration for the few listings you actually need. If you are greenfield, choosing an actively maintained admin panel removes the need for this package entirely.
- Does joy/voyager-datatable handle large datasets efficiently with server-side processing?
- That is not guaranteed. The package may not implement efficient server-side processing out of the box, and DataTables can strain client and server resources on large tables. Test with production-scale data volumes, add query indexes, enforce pagination limits, and consider caching before enabling it on high-traffic admin screens.
- Are there security risks with the DataTables integration in Voyager?
- Any DataTables integration carries risks of SQL injection through unvalidated search, sort, and filter parameters, plus cross-site scripting in rendered columns. Because this package has had no releases since February 2024, unpatched vulnerabilities will not be fixed upstream. Audit the query building and output escaping, whitelist sortable and searchable columns, and plan to maintain a patched fork for production.