Weave Code
Statamic Meilisearch Laravel Package
elvenstar/statamic-meilisearch
Integrates Meilisearch with Statamic, providing a fast, typo-tolerant search driver for your site's content. Configure indexes and searchable fields, then query results through Meilisearch while keeping Statamic collections and entries as the source of truth.
Meilisearch search driver for Statamic.
Frequently asked questions about Statamic Meilisearch
- How do I install the Meilisearch search driver for Statamic?
- Install it with Composer using composer require elvenstar/statamic-meilisearch, then publish the package config and point Statamic's search driver at Meilisearch. After that, define your indexes and searchable fields and backfill existing content. It is a normal Statamic addon with a service provider and publishable config, so it fits into a standard Laravel application without introducing a new runtime.
- Does this package support Laravel 13?
- Version 4.1.0 is described as a narrow release that adds Laravel 13 support, most likely by widening a Composer constraint. That only helps if Statamic core and your other addons are also Laravel 13-ready. Confirm whether Laravel 11 and 12 remain supported and whether the PHP floor moved before upgrading.
- How do I configure which Statamic collections and fields are indexed in Meilisearch?
- Indexes and searchable fields are defined in the package's publishable config. For each Statamic collection you choose the fields that are searchable, and optionally which fields are filterable and sortable. Design this before backfilling so you do not have to rebuild the index later.
- Is Meilisearch indexing synchronous or queue-driven, and what happens if Meilisearch is unreachable?
- The evaluated material does not confirm whether indexing is synchronous or queue-driven, or how the package behaves when Meilisearch is unreachable. Treat this as something to verify with the maintainer and in staging. Test by stopping Meilisearch and saving an entry, then check whether you get an exception, a silent skip, or a queued retry. In production, monitor failed jobs and searches so stale indexes do not go unnoticed.
- What is the upgrade path from v4.0.0 to v4.1.0 of this Statamic Meilisearch addon?
- Going from v4.0.0 to v4.1.0 is expected to be a lockfile-level bump with no behavioural change, but verify the diff. Update in a branch, let Composer resolve the constraint, run your test suite, and check search results against a seeded index. If you are not moving to Laravel 13, the release can be deferred.
- How does this compare to Statamic's built-in local search driver?
- Statamic's built-in local driver is simpler and has no extra infrastructure, which makes it the lower-risk choice for small sites. This package adds a stateful Meilisearch dependency in exchange for typo tolerance, fast querying, and faceted filtering on large catalogues. Adopt it when search is a first-class product surface, not when search is incidental.
- Which Meilisearch server versions are supported by this package?
- The supported Meilisearch server versions are not stated in the material reviewed, so check the README and composer.json. Pin your Meilisearch server version in development and production, and test index creation and querying against that exact version. Ask the maintainer which server versions are covered in CI.
- Do I need to reindex existing Statamic content after installing this Meilisearch driver?
- Yes. Installing the driver does not populate Meilisearch automatically for content that already exists. Plan an initial backfill of your collections, then confirm that new and updated entries are indexed as expected. Verify with a few known queries that results match Statamic entries.
- Is this package safe to use in production and is it actively maintained?
- The package is a single-maintainer addon under the rad-pack umbrella, so weigh bus factor and release cadence for anything on your critical search path. Pin a known-good version, watch releases, and have a plan to fall back to Statamic's built-in driver. Because search bugs show up as empty or stale results rather than exceptions, add monitoring.
- What PHP, Laravel, and Statamic versions does this package require?
- Check composer.json for the exact PHP, Laravel, and Statamic constraints before installing. The Laravel 13 support in v4.1.0 may also raise the PHP floor, and the required Statamic version for that combination should be confirmed. Test the full matrix in CI rather than assuming an upgrade is a no-op.
Weaver
How can I help you explore Laravel packages today?