- Is jgm/tablebundle compatible with Laravel?
- No. jgm/tablebundle is a Symfony bundle that relies on Symfony's Bundle registration, DI container compilation, and Twig templating, while Laravel uses a different service container, package discovery, and Blade. The v1.3.3 filter bugfix confirms filter rendering is implemented as a Twig extension, which is a hard dependency on the Symfony/Twig view layer. Adopting it in Laravel is a framework port, not a configuration exercise.
- How do I install jgm/tablebundle with Composer?
- You require the package with Composer and register the bundle in a Symfony application's bundle configuration; there is no Laravel package discovery or auto-registration. The repository README is the source of truth for the bundle class and setup steps. In Laravel you would need a Symfony/Twig bridge, which the technical assessment rates as a poor production path.
- Does jgm/tablebundle support Laravel 10 or Laravel 11?
- No. There is no Laravel version support because the package targets Symfony's bundle system. The codebase is a 2016-era Symfony 2.x/3.x and Twig 1.x codebase, and the v1.3.3 release contains narrow bugfixes rather than PSR-4 re-baselining or PHP 8 compatibility work. Laravel 10 and 11 would require a full port or reimplementation.
- Can I use jgm/tablebundle with Laravel Blade templates?
- Not directly. The package renders tables through Twig functions and extensions, including the filter Twig function that caused the error fixed in v1.3.3. Blade is a separate view layer, so the rendering code would have to be rewritten. The defensible option is to reimplement the declarative table pattern as a Blade component.
- Is jgm/tablebundle still maintained?
- Liveness is uncertain and the earlier archived-since-2016 claim should be re-verified directly on the repository. A v1.3.3 release exists with a named external contributor credited, but the changes are narrow bugfixes against an old codebase. There is no evidence of a compatibility policy, deprecation cycle, or security response process.
- Does jgm/tablebundle support sorting and pagination?
- The package blurb describes configurable columns, sorting, pagination, and Twig templates, but the implementation is tied to Symfony and Twig rather than Laravel's query builder or paginator. There is no Laravel-ready Eloquent pagination integration. In Laravel you would normally use Eloquent pagination plus a Blade table component instead.
- What are the best alternatives to jgm/tablebundle for Laravel?
- For Laravel, consider Filament tables, Livewire tables, or DataTables-style packages, or build a reusable Blade table component. If you need strictly server-rendered output with minimal or no JavaScript, a custom Blade component is often the closest match to this bundle's model. The assessment recommends reading TableBundle's source as a design reference and reimplementing the declarative table pattern rather than bridging it.
- Is jgm/tablebundle safe to use in production?
- The technical assessment rates overall risk as High: there is no CVE monitoring, no patch SLA, and no maintained vendor. The v1.3.3 release also shipped a breaking rename, TablieView::getActiveFilter to TableView::getActiveFilters, as a patch version, which is a semver violation. For production Laravel applications, do not adopt it directly.
- Why did jgm/tablebundle v1.3.3 break my code after composer update?
- Version 1.3.3 renamed the TablieView class to TableView and changed getActiveFilter to getActiveFilters, altering the return contract from singular to plural. That is a breaking change published as a patch release, so anyone pinned to ^1.2 and running composer update can silently break. Pin exact versions if you must use it and review the diff before upgrading.
- How should I test a Laravel port of jgm/tablebundle's table rendering?
- Extract the declarative table definition into a plain PHP class and unit test the column, row, and filter logic without any rendering. Then use Laravel HTTP tests or Blade component tests to assert the generated HTML output. This approach is far more testable than bridging Symfony's Twig extension into Laravel.