Weave Code
Ux Search Laravel Package
mezcalito/ux-search
mezcalito/ux-search adds a polished search experience to Laravel apps, with model indexing, customizable filters, and reusable UI components for search inputs and result lists. It helps you ship fast, relevant, typo-tolerant results without building search plumbing from scratch.
mezcalito/ux-search brings a polished, keyboard-friendly search experience to Laravel applications. It pairs a ready-made Blade/Livewire component with simple configuration, letting you register searchable models and surface results without building custom UI from scratch.
- Drop-in search component with keyboard navigation
- Configure searchable models and result mapping
- Tailwind-ready, customizable views
- Publishable config and views for full control
- Laravel-native integration with minimal setup
Frequently asked questions about Ux Search
- Is mezcalito/ux-search a Laravel package?
- No. mezcalito/ux-search is built as a Symfony UX package around Symfony's bundle system, Twig rendering, and Symfony UX interactivity, with faceted querying most likely tied to Doctrine. It ships no Laravel service provider, no Blade components, and no Eloquent adapter, so treating it as a Laravel package is a category mismatch rather than a small porting detail.
- Can I install mezcalito/ux-search in a Laravel app with Composer?
- Composer may resolve the PHP dependencies in a Laravel project, but that does not make it integrated. The package assumes Symfony bundle registration and Twig, and the registry shows zero dependents, so there is no community-proven Laravel integration path. Installing it directly is not recommended without a source review and a deliberate port or bridge plan.
- Does mezcalito/ux-search work with Blade and Eloquent?
- There is no built-in Blade or Eloquent support described. The package is Twig-oriented and its faceted query layer is likely Doctrine-based, while Laravel uses Blade and Eloquent. A Laravel implementation would require reimplementing the UI in Blade, likely with Livewire, and adapting any query logic to Eloquent or a Laravel search driver.
- What search backend does mezcalito/ux-search require?
- The overview does not specify the search backend, so this needs source review. It could be raw SQL LIKE queries, Doctrine's SQL filter API, or an external engine such as Elasticsearch, Meilisearch, or Algolia. That answer determines whether any part of the package is relevant to a Laravel stack.
- How do I add faceted search to Laravel instead of using this package?
- For Laravel, the practical default is Laravel Scout with Meilisearch, Typesense, or Algolia, optionally combined with Spatie's query builder for database-level facets. That gives you first-class Eloquent integration, maintained drivers, and a clear upgrade path. Only consider porting mezcalito/ux-search if its facet aggregation logic turns out to be genuinely differentiated.
- Can I port mezcalito/ux-search's facet logic to Laravel?
- Porting is feasible only if the package contains a framework-agnostic core for query parsing, facet aggregation, and filtering. If it does, extract that layer into a standalone namespace, wrap it in a Laravel service provider, and rebuild the UI in Blade plus Livewire. Budget it as fork-and-own work: roughly two to four weeks for simple facets, and materially more for hierarchical or range facets with URL state.
- Is mezcalito/ux-search production-ready and actively maintained?
- Treat it as high risk for production. It has around 66 stars, zero dependents, and a single-maintainer organization, which means no downstream validation and bus-factor risk. The listed 2026-08-19 release date is anomalous and should be verified against the repository's commit history. The MIT license is clean, but that is the only unambiguous positive signal.
- Does mezcalito/ux-search support Laravel 10 or 11, and what PHP or Symfony versions are required?
- There is no Laravel version support to check because the package targets Symfony. Instead, verify its PHP constraint and any Symfony or Doctrine version pins in composer.json, since Symfony packages often pin major versions tightly. Those constraints also determine how much of the dependency surface you would inherit in a port or sidecar.
- What are the best alternatives to mezcalito/ux-search for Laravel faceted search?
- If your stack is Laravel, use Laravel Scout with Meilisearch, Typesense, or Algolia, or Spatie's query builder for facet filtering, rather than adopting a Symfony UX bundle. If your stack is actually Symfony, mezcalito/ux-search is promising but unproven and worth a source review. Confirm the stack before spending further evaluation effort.
- How should I evaluate or test mezcalito/ux-search before adopting it?
- Start with source review: check for a framework-agnostic core, whether tests exist and run in CI, commit activity in the last 90 days, open issues and PRs, and the transitive dependency surface. Also verify the release date anomaly and the assumed search backend. A Symfony sidecar exposed over HTTP or JSON is technically possible, but it adds an operational component for a 66-star dependency and is rarely justified.
Weaver
How can I help you explore Laravel packages today?