Weave Code
Datatable Laravel Package
steelants/datatable
A Laravel package for building dynamic data tables with server-side processing, column configuration, and search support.
Laravel Package for creating simple Livewire data tables
Frequently asked questions about Datatable
- What Laravel and Livewire versions does steelants/datatable support?
- Check the package's composer.json for its laravel/framework and livewire/livewire constraints before adopting it, and confirm the last commit and release date. Packages this small usually target one Livewire major, so Livewire 2 to 3 upgrades are a real breakage risk. Pin exact versions of the package, Livewire, and Laravel in composer.lock.
- How do I install steelants/datatable in a Laravel application?
- Install it with composer require steelants/datatable, then rely on Laravel package auto-discovery for the service provider. You can optionally publish config and views if the package exposes them. Usage is typically a single Livewire component tag in a Blade view plus a column definition array.
- Does steelants/datatable support server-side pagination, sorting, and search?
- The package is built around Livewire's server round-trip model, so pagination, sorting, and search are intended to run server-side. Verify in the source that it paginates the query builder rather than hydrating the full collection into the Livewire component. Full hydration is a scaling problem on large tables.
- How do I scope queries for authorization with steelants/datatable?
- The package does not own authorization; you pass it a query or model source, so your application must supply an already-scoped Eloquent builder. Put the authorization scope in a policy, query scope, or dedicated method and hand only that builder to the table component. Never expose a raw model query that a user can influence.
- Is steelants/datatable maintained and safe for production use?
- Treat it as unvetted third-party code: it has very low community adoption, no visible downstream users, and a bus factor of one. For production, prefer forking and vendoring the source under its Apache-2.0 license so you control fixes and upgrades. Do not let it become the only implementation of authorization or data access.
- Can I use steelants/datatable with Inertia, Vue, or React?
- No. It is a Blade-rendered Livewire component, so it is an architectural mismatch for API-first, Inertia, Vue, or React front ends. Adopting it there would add Livewire as a new runtime concern just to render one table.
- How do I customize columns and cell rendering in steelants/datatable?
- Columns are configured through a definition array, with custom cell output typically handled by Blade views or callbacks. Confirm whether values are escaped by default and avoid raw HTML rendering unless you sanitize it, since that is an XSS exposure. Relationship columns and custom renderers are common weak spots in small table packages, so test them early.
- Does steelants/datatable work with Filament or existing Livewire components?
- It can coexist with Filament or existing Livewire components because it uses the same Livewire runtime, but confirm you do not end up with duplicate Alpine or Livewire script instances on the page. Also check that the package's Livewire major constraint matches the one Filament or your app already uses.
- How do I test a Livewire data table built with steelants/datatable?
- Use Livewire's testing helpers to mount the component, set search and sort properties, and assert the rendered rows and pagination state. Add tests around authorization scoping and escaping regardless of the package's own coverage, because the package's test suite is not a guarantee for your usage. Check whether the package ships tests before relying on it.
- What are the alternatives to steelants/datatable for Laravel data tables?
- Common alternatives are Filament tables, Livewire PowerGrid, Laravel Livewire Tables, or a hand-rolled Blade table, depending on whether your stack is Livewire-centric. If you are on jQuery DataTables or an Inertia front end, a Livewire package is usually the wrong tool. Compare maintenance activity, server-side processing, and authorization hooks before choosing.
Weaver
How can I help you explore Laravel packages today?