- Is kristofvc/list-bundle a Laravel package?
- No. It is a Symfony2 bundle built around AppKernel registration, DependencyInjection extension classes, compiler passes, services.yml conventions, and Twig. Laravel uses service providers, the Illuminate container, and Blade instead, and those share intent but not interfaces. There is no drop-in path, so the bundle's registration layer is dead code in a Laravel application.
- Can I install kristofvc/list-bundle in Laravel with Composer?
- No, not credibly. The bundle targets Symfony 2.x components at ~2.x, while Laravel pins modern symfony/console, symfony/http-foundation, and symfony/process. Composer will either fail to resolve the graph or force downgrades of packages Laravel itself depends on. There is no version of Laravel for which this installs cleanly.
- What does kristofvc/list-bundle actually do?
- It is a Symfony bundle for building paginated, sortable, and filterable structured data lists. You define list configurations once and reuse them across controllers and templates, with support for custom filters, column rendering, per-row actions, and flexible query building. The concept is useful, but the shipped code is legacy and archived.
- Which Laravel and PHP versions does kristofvc/list-bundle support?
- None officially, because it is not a Laravel package. It targets Symfony 2.x and PHP 5.4 to 5.6 era code, so expect no scalar or return types and probable use of constructs removed or deprecated in PHP 7 and 8. A Laravel 10, 11, or 12 application on PHP 8.1+ has no runtime surface in common with it.
- Is kristofvc/list-bundle maintained or safe for production?
- No. The last release was 2015-11-09, the repository is archived, and it has 0 stars and 0 dependents. Symfony 2.x reached end of life in 2016, with 2.8 extended support ending in November 2018. There is no security response process and no field testing, so technical risk is high and largely non-mitigable upstream.
- How do I port kristofvc/list-bundle to Laravel?
- Treat it as a reference implementation to read, not a dependency to install. First audit the source for substantive features like column definitions, row rendering, pagination, sorting, and per-row actions, and verify the license before adapting any code. Then map bundle configuration to config/list.php, Twig templates to Blade components or a view namespace, and service definitions to a service provider, and ship the result as an internal package with tests.
- What are the Laravel alternatives to kristofvc/list-bundle?
- Laravel-native options include Blade partials, Livewire, Filament tables, Yajra DataTables, and Laravel Nova. For many applications, a Blade component plus a query-builder trait covers pagination, sorting, and filtering in about a day. These options are maintained, tested, and designed for Laravel's container and view layer.
- Does kristofvc/list-bundle have a test suite or CI?
- Assumed no. There are no CI signals in the repository metadata, and zero dependents means zero field testing. If you port any logic, start with a feature inventory and write new tests rather than trusting the original code.
- Is kristofvc/list-bundle on Packagist and what license is it under?
- You must verify both before using or vendoring any code. An unlicensed repository cannot legally be vendored, so check the LICENSE file and confirm the package is actually published on Packagist under kristofvc/list-bundle. Record provenance if you adapt any source into a Laravel package.
- Can I run kristofvc/list-bundle as a sidecar Symfony app alongside Laravel?
- Technically possible, but disproportionate operational cost for a list-rendering feature. You would be maintaining a separate end-of-life Symfony 2 application, which carries high security and maintenance risk. The realistic path is a rewrite as a Laravel package or using native tools like Blade, Livewire, or Filament.