- How do I install timolake/livewire-tables in a Laravel application?
- Install it with Composer using composer require timolake/livewire-tables, then create a table class for the Eloquent model you want to display. In your Blade view, replace the existing manual loop with the package's table directive. There is no JavaScript build step or schema change required, so integration in a Livewire 3.x codebase is quick.
- Does timolake/livewire-tables support Laravel 11 and Livewire 3?
- Yes. The package targets Laravel 10 or 11 with Livewire 3.x and PHP 8.1 or newer, and it is Eloquent-backed with no frontend framework dependency. It fits best in Blade-based Livewire applications that are comfortable with Alpine and Tailwind. Inertia, React, and Vue stacks are a poor fit because the package assumes the Livewire component and Blade rendering workflow.
- Which version of timolake/livewire-tables should I pin in composer.json?
- Pin the 2.x line explicitly rather than relying on a floating constraint. Two lines ship in parallel, 1.18.x and 2.8.x, and they receive overlapping bug fixes such as session-key corrections in 1.18.1 and 2.8.1, so the choice should be documented. Release 2.4.3 existed only to add a Laravel requirement to composer.json, which suggests constraints were previously loose and should be locked on your side.
- What license is timolake/livewire-tables released under?
- The package reports NOASSERTION, meaning there is no declared, reviewable license. That is a blocking issue for commercial products until legal review is complete, especially because the package derives from danielbinsmaier/livewire-tables and coryrose/livewire-tables, whose terms also need to be compatible. Treat license clearance as the first gate before any integration work.
- Is timolake/livewire-tables actively maintained?
- Adoption signals are minimal, with 0 stars and 0 dependents, so it is effectively a single-maintainer package. If the author stops, your team owns the code, including any fork. Before the first merge, name an internal owner and decide whether you are prepared to maintain a fork.
- How does timolake/livewire-tables handle search, sorting, and large datasets?
- Search and sort are Eloquent query operations, with table state such as search, sort, page, and trashed filter persisted in the session. There is no virtual scrolling or server-side streaming, so performance depends on your indexes. It is fine to roughly 50,000 rows with proper indexing and unproven beyond about 100,000 rows with sub-second expectations.
- Does timolake/livewire-tables support CSV exports, multi-column sorting, or nested rows?
- No. Exports, multi-column sort, and nested or hierarchical rows are not included in the package, and none appear on its near-term roadmap. If those capabilities are on your two-quarter roadmap, plan to build them yourself or choose a different solution. The package is aimed at standard admin CRUD, audit logs, inventory, and moderation queues.
- Can I use timolake/livewire-tables with Inertia, React, or Vue?
- It is a poor fit for Inertia, React, or Vue stacks because it is designed around Livewire components and Blade views. The package integrates smoothly with Blade and works well alongside Alpine and Tailwind, with no separate JavaScript surface to negotiate. For public-facing or design-critical tables, the opinionated table-class convention can also work against you rather than for you.
- How do I test a datatable built with timolake/livewire-tables?
- Use Livewire's testing utilities to mount the component and assert the rendered rows, filtered search results, sort order, and pagination behavior. Session-persisted table state was introduced in 2.4.0 and has needed repeated fixes, so include assertions around state persistence and page resets when search or sort changes. Run those tests against the exact 2.x version you pin so upgrades surface regressions early.
- What are the alternatives to timolake/livewire-tables, and how do I migrate off it?
- The closest alternatives are the upstream projects it derives from, danielbinsmaier/livewire-tables and coryrose/livewire-tables, plus other Livewire table packages with larger communities. To keep an exit path, introduce an internal base table class so every screen inherits from your code rather than from Timolake classes. That wrapper layer turns adopting the package into a bounded pilot and makes a later swap or fork far cheaper.