- How do I install lunarphp/search in a Laravel Lunar storefront?
- Install it with Composer using composer require lunarphp/search. Because the package is still alpha, pin the version and review the README and release notes for the required Laravel Scout and Lunar configuration. You will also need a Scout-compatible search driver configured in your Laravel application.
- Does lunarphp/search work with Laravel Scout and Meilisearch?
- Yes. The package is built on Laravel Scout, and the 0.1.0-alpha.16 release adds a Meilisearch engine driver. You still need to configure Meilisearch and Scout in your Laravel application, and you should verify feature parity for filters, sorting, and pagination against the other driver.
- What Laravel versions does lunarphp/search support?
- The provided context does not list exact Laravel version constraints, so check the package composer.json and README before adopting it. It is designed for Laravel applications running Lunar storefronts and relies on Laravel Scout. Because it is alpha, confirm compatibility with your app's Laravel and Scout versions rather than assuming broad support.
- How do I configure product and variant indexing for Lunar search?
- Indexing is handled through Laravel Scout, and lunarphp/search indexes Lunar products and variants for Scout-compatible drivers. Configuration is intended to remain reusable across storefronts rather than being hard-coded into search pages. Review the package configuration and Scout searchable setup, then run your Scout import commands.
- Can I filter and sort search results with lunarphp/search?
- Yes. The package provides a reusable query layer that supports filters, sorting, and pagination for catalog results. That lets storefront search pages and product listings stay decoupled from the underlying search engine. Exact filter syntax and sort options depend on the configured driver and should be tested per engine.
- Is lunarphp/search stable enough for production?
- Treat it as alpha: 0.1.0-alpha.16 has no stable API guarantee, and search abstractions can churn between pre-releases. It can be suitable for prototypes or controlled rollouts, but production use should include version pinning, integration tests, and a rollback plan. Evaluate the single-contributor risk around newer drivers such as Meilisearch before committing.
- How do I switch search engines or reindex without downtime?
- Switching engines generally requires a full product and variant reindex because each search backend maintains its own index. The context does not document migration tooling or downtime guarantees, so plan a parallel-run cutover and a feature-parity sign-off. Because the driver is additive, you are not forced to migrate an existing engine immediately.
- Does lunarphp/search support pagination in storefront search pages?
- Yes. Paginated results are part of the package's reusable query layer alongside filters and sorting. This is intended for search pages and product listings in Lunar storefronts. Confirm pagination semantics against your chosen Scout driver, since engines can differ in page limits and result counting.
- Are there tests for multiple search engine drivers?
- The provided context does not confirm contract-level or integration tests that run against both engines, and Meilisearch coverage may be manual. With two drivers, behavioral differences in filtering, ranking, typo tolerance, and pagination are a real concern. Ask maintainers for the test matrix and add your own integration tests around critical catalog queries.
- What are alternatives to lunarphp/search for Laravel ecommerce search?
- Alternatives include using Laravel Scout directly with your own Lunar product searchable models, or adopting a search service SDK without the Lunar query layer. The value of lunarphp/search is its reusable Lunar-specific query layer for filters, sorting, and pagination across Scout drivers. If you need a stable API today, compare it with a mature standalone search integration and account for the alpha status here.