Weave Code
Meiliscout Laravel Package
amphibee/meiliscout
MeiliScout is a Laravel Scout driver that connects Eloquent models to Meilisearch for fast, typo-tolerant full-text search. It supports indexing, filtering, sorting, pagination, and familiar Scout APIs, making it easy to add powerful search with minimal configuration.
At a glance
Frequently asked questions about Meiliscout
- Is amphibee/meiliscout actually a Laravel Scout driver?
- Despite the Composer name and the Scout/Meilisearch framing in its description, the 2.5.0 release is unambiguously a WordPress plugin. It ships global functions like meiliscout_register_suggest() and meiliscout_suggest(), a WP-CLI command (wp meiliscout check-suggest), an admin screen under MeiliScout › Suggestions, and Gutenberg block registration. There is no Scout engine contract, no Laravel service provider, and no model index registration in the codebase. Treat the Laravel packaging claim as inaccurate until you have inspected the specific tagged release yourself.
- Does it work with Laravel Scout out of the box?
- No. Laravel Scout resolves its engine through the scout.driver binding, and this package registers nothing at that seam. Instead it owns an entire WordPress vertical: index schema, admin UI, REST namespace /meiliscout/v1/, block registration, browser client, and WP-CLI commands. None of that surface is reachable from a Laravel application, so installing it would give you a plugin's PHP files and no usable search engine.
- Which Laravel versions does this package support?
- There is no reliable answer because there is no Laravel integration present to version-constrain. No Illuminate service provider, config file, or facade is registered in the 2.5.0 code, so the usual Laravel version compatibility question does not apply. If you find a composer.json on the tag, read its require and extra.laravel blocks before assuming anything, and expect an empty or WordPress-oriented result.
- How do I install amphibee/meiliscout in a Laravel app?
- You can run composer require amphibee/meiliscout, but doing so in a Laravel application will not give you a working Meilisearch driver. The package expects a WordPress runtime with its own hooks, REST routes, and admin screens, so functionality simply will not boot under Laravel. The practical install path for this code is as a WordPress plugin in a WordPress site.
- Does it support filtering, sorting, and pagination?
- Filtering, sorting, and pagination are implemented inside the WordPress product against its posts and taxonomies indexes, not as a Scout query builder API you can call from Eloquent. There is no searchable(), where(), orderBy(), or paginate() chain being registered on a Laravel engine here. If you want those behaviours in Laravel you would be writing your own query layer directly against Meilisearch using meilisearch/meilisearch-php.
- Can it index my Eloquent models?
- No. The package indexes WordPress posts and taxonomies and exposes a fixed document schema (currently schema 6, including fields such as thumbnail with url, width, height, and alt, or null). There is no toSearchableArray() handling, no model observer wiring, and no Scout index sync command. Indexing Eloquent models would require the official Scout Meilisearch engine instead.
- What are the security considerations for production?
- The 2.5.0 surface includes tenant-token minting against a search-only Meilisearch key exposed through the WordPress REST routes /meiliscout/v1/suggest/{id}/token and /suggest/{id}/search. Verify that the token route is authenticated and nonce-protected, that token TTLs are short, and that minting is rate-limited, otherwise your Meilisearch quota becomes a free public API. Separately, template rendering accepts raw HTML and js:<name> values; if any of those are stored in an option editable by a lower role, that is stored XSS. Get an explicit answer on both before exposing anything to the internet.
- What should I use instead for Meilisearch in Laravel?
- Laravel Scout ships a first-party Meilisearch engine, so you can set SCOUT_DRIVER=meilisearch and point it at your instance with no third-party driver required. For lower-level control, meilisearch/meilisearch-php gives you direct index management, filterable and sortable attribute configuration, and typo-tolerance settings. Both are maintained in the open with predictable release cadence, which is the main thing this package does not offer a Laravel team.
- How do I test or verify a MeiliScout installation?
- In its actual WordPress context the package provides a diagnostics admin screen and a CLI check you can run with wp meiliscout check-suggest. There is no comparable testing hook for Laravel, no engine fake, and no Scout::fake() integration to assert against. Any Laravel-side test suite would have to mock Meilisearch itself rather than this package.
- Is there any scenario where a Laravel app should depend on this?
- Only indirectly, in a WordPress-as-content-backend architecture where WordPress produces the indexes and a Laravel delivery tier reads them. Even then the package is not a dependency: its schema-6 document shape becomes a contract you consume read-only, pinned to that version, and your query parity tracks another team's release cadence. That is a narrow, cheap read-only evaluation, not adoption, and it requires confirming field names, index naming, and ranking rules first.
Weaver
How can I help you explore Laravel packages today?