Weave Code
Autocompleter Bundle Laravel Package
pugx/autocompleter-bundle
PUGXAutocompleterBundle adds AJAX-powered autocomplete fields to Symfony forms, with built-in Doctrine entity support and jQuery UI integration. It handles suggestions, entity-to-label conversion, and form wiring, making it easy to replace select boxes or text inputs with searchable autocomplete wid...
PUGX AutocompleterBundle adds AJAX-powered autocomplete fields to Symfony forms. It integrates jQuery UI Autocomplete with configurable Doctrine ORM queries, letting users search and select entities from a remote endpoint without loading full lists.
- Reusable Autocomplete form type
- Configurable Doctrine entity lookups
- Built-in AJAX endpoint controller
- Customizable labels, routes, and minimum input length
- Simple integration with existing Symfony forms
Frequently asked questions about Autocompleter Bundle
- Is pugx/autocompleter-bundle a Laravel package?
- No. Despite being distributed via Composer and often lumped in with PHP packages, PUGXAutoCompleterBundle is a Symfony bundle that hooks into the Symfony Form component, dependency injection container, routing, and Twig rendering. Installing it in a Laravel application would mean pulling in the Symfony Form stack as a dependency, which is an anti-pattern in a Laravel codebase. If your target is Laravel, treat this as a concept to reimplement natively rather than a package to require.
- How do I install PUGXAutoCompleterBundle in a Symfony application?
- Run composer require pugx/autocompleter-bundle, then enable the bundle in config/bundles.php. Add the bundle configuration (route prefix and default widget options) and replace or augment an existing EntityType or ChoiceType with AutocompleteType in the form you want to enhance. Finally, implement or verify the controller action that returns the JSON payload in the shape the widget expects, and confirm the bundle's assets load through your Webpack Encore or Vite pipeline.
- Which Symfony and PHP versions does PUGXAutoCompleterBundle support?
- Do not assume support from the README alone: check the require constraints in the package's composer.json and confirm the release history on Packagist before committing. Bundles of this vintage frequently lag major Symfony releases, so an older constraint can become a hard pin on your framework upgrade path. Run composer why-not or a dry-run update against your current Symfony version as a quick compatibility check.
- What front-end library does the bundle use for the autocomplete widget?
- The bundle wraps jQuery UI Autocomplete, which is in maintenance mode and is disallowed in many modern front-end standards. That legacy dependency is the single biggest adoption blocker, and jQuery and jQuery UI version skew against your existing front-end is a common failure mode. If jQuery UI is not permitted in your stack, plan to replace the widget layer or pick a bundle built on a modern library instead.
- How do I implement autocomplete fields in Laravel instead of using this bundle?
- Build it natively: a controller route that returns JSON for a search term, plus a modern widget such as Tom Select, Select2, or an Alpine/Livewire component. The work is typically one to two days and removes both the jQuery UI dependency and the LGPL licensing constraint. This approach also gives you full control over authorization, query bounds, and rate limiting on the endpoint.
- Is PUGXAutoCompleterBundle actively maintained and safe for production?
- The adoption signal is weak, with roughly 92 GitHub stars and zero dependents, which suggests the bundle is niche or effectively unmaintained. Verify the actual release dates and commit cadence on Packagist and GitHub rather than trusting a single anomalous timestamp. If you proceed, pin the version, put the feature behind a flag, and budget for a fallback in case maintenance stops.
- What are the licensing implications of LGPL-3.0 for this bundle?
- LGPL-3.0 is generally workable for unmodified dynamic use inside an application, but static bundling, forking, or modifying the library triggers copyleft obligations. The obligations differ depending on whether you deploy as SaaS, on-premise, or distribute the code to customers. Get legal sign-off for your specific deployment model before adopting it.
- How do I secure the autocomplete JSON endpoint against abuse?
- The endpoint performs a database query on every keystroke, so it needs explicit authentication, per-field authorization, and strict input validation. Always cap the number of returned results with a LIMIT and apply rate limiting per user or session. The bundle itself does not solve any of this, so these controls are your responsibility.
- Can I use a custom data source instead of a Doctrine entity?
- Yes. The bundle supports repository callbacks and custom data sources, so you are not restricted to a single Doctrine entity query. Your callback must return results in the JSON shape the widget expects, usually an id and a label. Enforce authorization and result caps inside the callback, because the per-keystroke query path is the main security surface.
- What are the alternatives to PUGXAutoCompleterBundle?
- For Symfony, Symfony UX Autocomplete is the modern replacement: it is built on Tom Select, avoids jQuery UI, and integrates cleanly with AssetMapper or Encore. You can also wire Tom Select or Select2 directly to a small JSON controller action, which is easy to test and secure. For Laravel, skip the bundle entirely and build the controller plus a modern widget natively.
Weaver
How can I help you explore Laravel packages today?