- Does livewire-smart-table support Laravel 10, 11 and Livewire 3?
- The last tagged release is from February 2023, which predates Livewire 3, so assume it is Livewire 2 only until you verify otherwise. Check the composer.json constraints for the livewire/livewire and illuminate/support requirements rather than trusting the README. Test it in a throwaway Laravel app on your exact version matrix before committing, because a Livewire 3 project will likely need a fork or port.
- How do I install tkaratug/livewire-smart-table with Composer?
- Run composer require tkaratug/livewire-smart-table, then publish the package config and Blade views only if you need to override the defaults. You then define a Livewire component that returns a query builder plus a column set and render the table component in your Blade view. A first working grid is realistically a one-to-two-day task for a competent Laravel developer.
- Is livewire-smart-table still maintained in 2025?
- The repository shows roughly 92 stars, no dependents and no release since February 2023, which points to a dormant project rather than an actively triaged one. That means no ongoing bug fixes or security patches from upstream. If you adopt it, plan to vendor or fork the MIT-licensed source so you control the release cadence.
- What are the best alternatives to livewire-smart-table for Laravel?
- Rappasoft Livewire Tables and Filament Tables are the usual replacements, both with far larger install bases and current Livewire support. Both ship sorting, filtering, pagination, bulk actions and exports out of the box. They are heavier dependencies, but active maintenance matters for long-lived admin panels.
- How do I add sorting, searching and pagination to a Livewire table without extra JavaScript?
- This package bundles sorting, searching and pagination, so you supply a query builder and column definitions instead of writing query logic yourself. All interactions run inside the Livewire component lifecycle, meaning each sort, search or page change is a server round-trip. That is fine for internal admin screens but not for high-concurrency or SPA-fronted surfaces.
- Can I customize columns and render custom HTML in livewire-smart-table?
- Columns are configurable, and you can render custom HTML per cell through column renderers or published Blade views. That flexibility is the main value, but every renderer, filter and bulk action you add turns the package into an in-house framework you cannot cheaply patch. Keep column and filter definitions in application-level classes so a future migration stays manageable.
- Does livewire-smart-table handle large tables or server-side pagination?
- Confirm empirically that it paginates server-side and does not hydrate the full result set before you point it at a big table. Test with your largest realistic table — row count, column count and relationship depth — and eager-load relationships in the query you pass in. Because each interaction is a Livewire round-trip, the component fits internal admin grids rather than customer-facing, high-traffic views.
- Is livewire-smart-table safe to use in production?
- It is small and MIT licensed, but there have been no releases since early 2023, so you get no security-patch stream and no fixes for Livewire major upgrades. Audit whether filter or search input reaches whereRaw or any unparameterized SQL clause before exposing it to untrusted users. Pin the Composer version and keep a fork under review if you ship it.
- How do I publish and configure the livewire-smart-table views and config?
- Use the standard vendor:publish command with the package's service provider tag to publish its config and Blade views. Publishing is optional since the package ships working defaults, so only publish when you need to change templates, styling or default page sizes. Keep published views in version control so upgrades and forks stay reviewable.
- Can I fork livewire-smart-table or use it with Livewire 3?
- The MIT license permits a private fork, and given the release cadence that is probably the realistic route to Livewire 3 support. Porting means updating hydration and lifecycle hooks for Livewire 3 and retesting wire: directives plus any published Alpine.js assets. Assign an internal owner and review cadence first, or you simply inherit an unmaintained dependency with your name on it.