- Does guikingone/meili-search-bundle work with Laravel?
- No. It is a Symfony bundle whose entire value is Symfony-flavored wiring: a Bundle subclass, a DI extension, a semantic meili_search config tree, compiler passes, and service tagging. None of those concepts exist in Laravel, so there is nothing for a Laravel app to consume. Laravel applications should use Laravel Scout's first-party Meilisearch driver instead.
- How do I install guikingone/meili-search-bundle?
- You install it with Composer, register the bundle in Symfony's bundles.php, and configure it under the meili_search key. There is no Laravel ServiceProvider, no publishable config, and no facade. Note that the package has had no release since 2020-11-02, so installation on a modern Symfony or Laravel stack is not a supported path.
- Which Laravel versions does this package support?
- None officially. A 2020-era Symfony bundle typically pins symfony/* 4.4 or 5.x and PHP 7.4 through 8.0, which conflicts with Laravel 10 and 11 on PHP 8.1+ and Symfony 6/7 components. Treat this as incompatible rather than as something that merely needs testing.
- Which Meilisearch server version is this bundle compatible with?
- Most likely the pre-1.0 Meilisearch 0.20 or 0.21 line, which is what existed when the bundle was last released. The 1.0 transition and later releases changed the task API, index settings payloads, ranking-rule semantics, and typo-tolerance configuration. A current Meilisearch server will probably reject or silently reinterpret the assumptions the bundle encodes.
- Is guikingone/meili-search-bundle still maintained?
- No. The last release was 2020-11-02, roughly five years ago, with about 11 stars, zero dependents, and a single maintainer. That means no patches for Meilisearch SDK or server drift and no community to ask for help. There are also no reference implementations, adapters, or blog posts to lean on.
- What is the Laravel alternative to this Symfony bundle?
- Use laravel/scout with its first-party Meilisearch driver, which has shipped since Scout 9 and wraps the official meilisearch/meilisearch-php SDK. Configure config/scout.php, implement searchableAs() and toSearchableArray() on your models, and run scout:import. That path is actively maintained and takes roughly half a day to configure, versus an estimated 3 to 6 dev-days to force-fit this bundle.
- Can I port this Symfony bundle to Laravel?
- You could, but you would be discarding the only thing the package provides, which is Symfony container wiring, and re-wrapping the official SDK you could depend on directly. A port would need a ServiceProvider, publishable config, a facade, and possibly a Laravel Scout Engine implementation. The result is a bespoke wrapper with no upstream, no dependents, and no one to maintain it.
- How do I migrate index configuration from this bundle to Laravel Scout?
- Extract the declarative index settings: primary key, searchable, filterable, and sortable attributes, ranking rules, synonyms, and stop words. Move them into config/scout.php plus searchableAs() and toSearchableArray() on your models. Rebuild the index with scout:import, dual-write during cutover, and then remove the bundle and its transitive Symfony constraints.
- How do I test a Meilisearch integration like this in CI?
- Testing a 2020-era bundle against a current Meilisearch server mostly proves incompatibility, and its Symfony test tooling does not carry over to Laravel. In a Laravel app, run a pinned Meilisearch container in CI and use Scout's testing helpers to assert indexing and search behaviour. There is no bundle-specific test suite or reference implementation to rely on because the package has zero dependents.
- What are the production risks of adopting this package?
- The risks are staleness against Meilisearch server drift, incompatible PHP and Symfony constraints, zero community support, and no clear owner for a fork. The server version you target, not the client, determines viability. If you adopt anyway, define who owns patches and the patch SLA; in practice the answer is usually nobody, which answers the question.