- Is kreyu/data-table-bundle a Laravel package?
- No. kreyu/data-table-bundle is a Symfony bundle, not a Laravel package. It depends on Symfony components such as DependencyInjection, HttpKernel, Twig, and OptionsResolver, so it does not plug into Laravel's service provider, Blade, or Eloquent model directly.
- Can I use Kreyu DataTableBundle in a Laravel application?
- Only with significant adaptation. A Laravel integration would need to bridge or replace Twig rendering, Symfony request and options handling, bundle registration, routing, and frontend asset assumptions. For a Laravel-only stack, it is not a drop-in Composer dependency.
- What features does Kreyu DataTableBundle offer?
- It provides declarative data tables with columns, filters, row and bulk actions, sorting, pagination, searching, AJAX loading, and built-in exports. It also includes themeable templates for Bootstrap, Tailwind, or custom designs. These features are configured through a PHP API and Twig integration.
- Which data sources does Kreyu DataTableBundle support?
- It supports Doctrine ORM, Doctrine DBAL, plain arrays, and Elastica sources. That makes it useful for Symfony applications already using Doctrine or Elasticsearch. Laravel's Eloquent is not a supported source out of the box.
- Does Kreyu DataTableBundle work with Laravel Eloquent?
- No, Eloquent is not a native data source for this bundle. The documented sources are Doctrine ORM/DBAL, arrays, and Elastica. Using Eloquent would require a custom adapter or a separate query and table layer.
- What are Laravel alternatives to Kreyu DataTableBundle?
- For Laravel-native tables, evaluate Filament tables, Livewire-based table components, or an internal query and table builder. These options align with Blade, Eloquent, and Laravel's request lifecycle. They avoid the cost of bridging Symfony runtime contracts.
- How difficult is integrating Kreyu DataTableBundle with Laravel?
- Direct integration is medium-to-high effort. You would need to handle Twig rendering, Symfony request and options resolution, bundle registration, routing, and asset assumptions. A proof of concept should target one table end to end before committing.
- Does version 0.33.0 add Laravel support?
- No. v0.33.0 adds Symfony 8 support and includes minor Twig and asset fixes, such as removing an unnecessary Bootstrap modal import and fixing a Twig deprecation. It is a maintenance release and does not introduce Laravel integration points.
- Can I run Kreyu DataTableBundle as a Symfony service behind a Laravel frontend?
- Yes, that is a more viable pattern if your organization already operates Symfony services. You can expose the table layer behind an API and render the results in Blade. This keeps the Symfony bundle behind a clear service boundary instead of embedding it in Laravel.
- Is Kreyu DataTableBundle actively maintained and safe to adopt?
- It is MIT licensed, so legal risk is low. v0.33.0 shows active maintenance and Symfony 8 compatibility work, but Laravel compatibility is not claimed and Laravel production usage evidence is limited. Validate release metadata, test coverage, and the supported Symfony and PHP matrix during a spike.