- Is lifo/autocomplete-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It relies on Symfony kernel features such as bundles.php registration, container compilation passes, Symfony routing, and typically Doctrine ORM repositories. Laravel has no equivalent bundle system, so you should treat this repository as a reference implementation rather than a Laravel dependency.
- Can I install lifo/autocomplete-bundle in a Laravel application with Composer?
- A direct composer require into a Laravel project will either fail dependency resolution or install inert code that never boots. The package expects a Symfony kernel and Doctrine data sources, which Laravel does not provide. Making it work would require a fork that replaces the bundle class with a service provider and rewires the data layer to Eloquent.
- What does lifo/autocomplete-bundle actually do?
- It adds AJAX-powered autocomplete fields to Symfony forms with minimal configuration. You point a form type at a Doctrine repository or custom callback, and the bundle handles the JSON endpoint, query filtering, and result formatting. It also ships a JSON controller compatible with Select2 and jQuery UI, plus optional caching for frequently queried datasets.
- Which Symfony and PHP versions does lifo/autocomplete-bundle support?
- The repository does not document current version support clearly, and packages of this vintage commonly pin Symfony 2.x or 3.x with PHP 5.6 to 7.x constraints. Those constraints conflict with modern Laravel requirements of PHP 8.2 and above. Confirm the exact composer.json constraints before assuming any compatibility.
- Does lifo/autocomplete-bundle have tests, CI, or an active maintainer?
- There is no evidence of a test suite, CI configuration, or an active maintainer. The project shows zero stars, zero dependents, and no demonstrated production use or community validation. For an endpoint that accepts user-controlled query strings, that lack of maintenance is a material risk.
- How would I build autocomplete in Laravel if this bundle is Symfony-only?
- Build it natively: a throttled GET route pointing at an invokable controller, a bounded LIKE or full-text Eloquent query, a normalized JSON response shape, and a client-side typeahead library. The bundle's controller logic and response conventions are useful reading material for scope, but the integration layer must be rewritten. Most teams find this is a small, well-understood feature rather than a package problem.
- Does the autocomplete endpoint sanitize query input and enforce a result limit?
- The evaluation flags this as an open question that must be answered by source review before any reuse. Unvalidated input passed into a Doctrine query builder is a live injection and enumeration surface. If you borrow the pattern, enforce parameter binding, a hard result cap, and request throttling in your Laravel implementation.
- Is lifo/autocomplete-bundle compatible with Laravel Scout or Eloquent?
- No. The bundle is built around Doctrine repositories and Symfony form types, so it has no awareness of Eloquent models or Scout drivers. Laravel-native autocomplete is usually Scout plus a thin JSON controller, or a query-builder scope behind a rate-limited route. Treat the bundle as a design reference for the endpoint contract, not as a Scout integration.
- What are Laravel-native alternatives to lifo/autocomplete-bundle?
- The practical path is Laravel Scout with a frontend typeahead library, or a roughly 150-line custom endpoint backed by an Eloquent scope and cache. Both give you the same JSON contract the bundle provides, without a Symfony kernel. The autocomplete category scores well for portfolio value, so the need is real even though this specific artifact is weak.
- Is it worth forking lifo/autocomplete-bundle for a Laravel project?
- Forking is moderate feasibility as a reference base but not as a drop-in, and the effort is roughly equivalent to building the feature yourself. You would replace the bundle class with a service provider, move configuration into config/autocomplete.php, and reimplement the data layer against Eloquent. The MIT license removes legal friction, but permissive licensing does not offset an unmaintained dependency.