- Is liz/dependent-select-bundle compatible with Laravel?
- No. Despite being listed among Laravel packages, liz/dependent-select-bundle is a Symfony bundle forked from evercodelab/dependent-select-bundle. It depends on Symfony's form component, dependency injection container, event dispatcher, and likely Doctrine ORM, none of which map to a Laravel application. There is no Laravel service provider, facade, publishable config, or Blade integration.
- How do I install liz/dependent-select-bundle?
- You would normally install it with Composer inside a Symfony project, but it is an unmaintained fork with no release cadence. In a Laravel project Composer will likely fail dependency resolution because of old Symfony and PHP constraints. The realistic path is not to install it but to port the cascading-select pattern into Laravel using a JSON endpoint and Alpine.js or Livewire.
- Which Laravel versions does liz/dependent-select-bundle support?
- None. The package targets the Symfony 2.x/3.x era and probably pins PHP 5.x to 7.x constraints, so it cannot satisfy Laravel 10 or 11 requirements of PHP 8.1+ and modern Symfony components. Assume incompatible until its composer.json proves otherwise.
- What is the best Laravel alternative to liz/dependent-select-bundle?
- Build the behavior directly in Laravel: a thin controller that returns JSON options for a parent ID, an Eloquent mapping table for parent-child pairs, and a small Alpine.js or Livewire component to repopulate the child select on change. This gives you testable, owned code in one to three engineering days. Livewire, Filament, and select2 AJAX are common choices for the front end.
- Does liz/dependent-select-bundle work with Blade or Livewire?
- No. It integrates with Symfony Forms and Twig-rendered templates, and its front-end assets are jQuery-era JavaScript files. There is no Blade directive, Livewire component, or modern asset-pipeline support. For Laravel you should use Livewire or Alpine.js instead.
- Is liz/dependent-select-bundle safe for production?
- High risk. It has zero stars, zero dependents, and is a single-user fork of an unmaintained upstream with no issue triage or security patching. An unmaintained, low-visibility fork is exactly what Composer security audits and malware scanners flag. Do not add it to a production Laravel application.
- Can I use liz/dependent-select-bundle with Eloquent instead of Doctrine?
- Almost certainly not without rewriting it. The bundle is likely built around Doctrine ORM entity repositories to resolve child options, which conflicts with Eloquent. You would have to replace its data layer, at which point porting the pattern is cheaper and safer.
- How do I test dependent select fields in Laravel?
- Test the server endpoint with HTTP tests: assert that GET /api/options/{parentId} returns the correct JSON for authorized users and an empty or 403 response otherwise. Test the mapping table with database assertions and seeders. For the front end, use Livewire tests or Laravel Dusk to verify the child select repopulates on parent change.
- What PHP and Symfony versions does liz/dependent-select-bundle require?
- Expect PHP 5.x to 7.x and Symfony 2.x/3.x constraints inherited from the upstream bundle, plus a probable Doctrine ORM requirement. Those constraints fail Composer resolution against Laravel 10/11 on PHP 8.1+ and Symfony 6/7. Check its composer.json, but assume version rot.
- Is liz/dependent-select-bundle maintained?
- No. It is a fork of evercodelab/dependent-select-bundle with no release cadence, no issue triage, and no security patching. The upstream targets an old Symfony era, and the fork shows no sign of active maintenance. Treat it as abandoned and migrate the capability, not the code.