Weave Code
Dependent Select Bundle Laravel Package
evercodelab/dependent-select-bundle
Symfony bundle for dependent select fields: dynamically load and update dropdown options based on another field’s selection, simplifying cascading forms with AJAX-backed choices.
This bundle helps to create dependent AJAX fields for Symfony forms
Frequently asked questions about Dependent Select Bundle
- Can I use evercodelab/dependent-select-bundle in a Laravel application?
- No. It is a Symfony bundle that hooks into the Symfony Form component, bundle registration, and form events, none of which exist in Laravel's default stack. Composer may resolve the library, but there is no supported way to make it work inside a Laravel request lifecycle without reimplementing its core logic. For a Laravel codebase, treat it as a non-starter.
- How do I install evercodelab/dependent-select-bundle?
- You would normally require it with Composer and register the bundle in config/bundles.php inside a Symfony application. That registration step is Symfony-specific and has no Laravel equivalent. Even in Symfony, the package's age and dependency constraints make a clean install unlikely on modern framework versions without overrides.
- Does this package support Laravel 10 or Laravel 11?
- It does not support any Laravel version. The package targets Symfony forms and Symfony's bundle system, not Laravel's service container, routing, or validation. If you are evaluating it for a Laravel 10 or Laravel 11 project, there is no compatible integration path.
- How do I create dependent or cascading select fields in Laravel?
- Use a native Laravel approach instead of a Symfony bundle. Livewire with wire:model.live on the parent field and computed child options is the closest analogue and keeps the logic server-side. If your app already uses Inertia, a small JSON endpoint plus a Vue or React component works well, and Alpine.js with a thin JSON route is a minimal Blade-native option.
- Is evercodelab/dependent-select-bundle abandoned or maintained?
- The package shows the hallmarks of an abandoned artifact: zero stars, zero dependents, and no visible maintenance activity. An unmaintained bundle that defines HTTP routes for AJAX field population receives no security triage. That makes any pinned Symfony or jQuery dependency a long-term liability rather than a stable foundation.
- Which Symfony versions does this bundle support?
- The evaluation notes that bundles from this lineage typically pin symfony/symfony to 2.x or 3.x-era constraints. A modern Symfony 6 or 7 application cannot install it without constraint overrides. Verify the composer.json constraints before assuming it will run on a supported Symfony release.
- How do I test dependent select behavior in Laravel?
- Keep the cascade logic server-side so it is testable with Laravel's HTTP and validation tests. With Livewire you can assert the child options update after setting the parent value, and with a JSON endpoint you can feature-test the route's response and authorization. This is far cheaper than reverse-engineering undocumented edge cases in a third-party bundle.
- What are the alternatives to this bundle for Laravel developers?
- Livewire, Inertia with Vue or React, and Alpine.js with a small JSON route are the practical alternatives. Each reproduces the bundle's value in well under a sprint and gives you code your team owns. You also avoid a jQuery front end that conflicts with modern asset pipelines and Content Security Policy settings.
- Can I use this bundle with Livewire or Inertia?
- No. Livewire and Inertia are Laravel-side tools, while this bundle depends on Symfony form types and form event listeners. There is no bridge between the two, and building one would mean rewriting the bundle's behavior anyway. Implement the cascade directly in Livewire or your Inertia components instead.
- What are the production risks of depending on this bundle?
- The main risks are unpatched security advisories in its pinned Symfony or jQuery dependencies and hard framework constraints that block future upgrades. Dependent-select logic also has tricky edge cases, such as resetting invalidated children and preserving server-side validation on edit forms, that are expensive to trust when undocumented. If a Symfony app already uses it, plan a migration off it rather than a migration to it.
Weaver
How can I help you explore Laravel packages today?