Statamic Live Search Laravel Package

Product Decisions This Supports

• Build vs. buy for search: v3.2.0 confirms this package is actively tracking the two platforms it serves (Laravel 13, Statamic v6). That maintenance signal is the main input to a "buy/adopt" call over building an in-house search layer — an internal build would carry the same framework-upgrade tax without the upstream support.
• Platform upgrade sequencing: Support for Laravel 13 and Statamic v6 in the same minor release means search does not become a blocker on a framework or CMS upgrade. This is directly actionable for roadmap planning: the search dependency can be treated as "green" in the upgrade readiness matrix rather than a line item requiring remediation work.
• Use cases this unlocks: content/keyword search across a Statamic or Laravel-backed site — site search, content discovery, admin-side lookup. Appropriate where search is a supporting feature, not the core product differentiator.
• Deprecation/support policy input: A minor-version release carrying two major platform-compatibility additions suggests the maintainer absorbs platform churn rather than deferring it to a major. That reduces the expected cost of staying current and is worth recording as a standing assumption in the dependency policy.
• Low-priority code-quality signal: The typed $q declaration is hygiene, not a feature. It matters mainly as evidence of ongoing maintenance discipline — a package receiving small correctness patches alongside compatibility work is less likely to be abandoned.

When to Consider This Package

Adopt when:

• The application is on Laravel (up to 13) or Statamic (up to v6), and search is a supporting capability rather than the product's core value.
• You want a dependency that moves with framework majors on a minor release cadence, so upgrades don't require a parallel search migration.
• Requirements are content/keyword search without heavy relevance tuning, vector/semantic retrieval, or complex faceting.

Look elsewhere when:

• You need advanced relevance control, typo tolerance at scale, synonyms, or analytics-driven ranking — a dedicated search service (Meilisearch, Typesense, Algolia, Elasticsearch) is the better fit, and this package becomes an integration layer at best.
• You are pinned to Laravel ≤12 or Statamic ≤5 and cannot absorb a major upgrade; verify the supported version matrix before committing, since this release extends the range rather than redefining it.
• You extend or subclass the Search component: the newly typed $q property is a minor-version change, but any subclass assigning null or a non-string to it will now fail. Audit extensions before upgrading — low blast radius, but not zero.

How to Pitch It (Stakeholders)

For executives: This package is a low-risk, actively maintained dependency for site search. Its latest release adds compatibility with the next major versions of Laravel (13) and Statamic (6), which means our planned platform upgrade won't be held up by search. No migration, re-licensing, or re-architecture is implied.

For engineering: v3.2.0 is a compatibility and hygiene release — Statamic v6 and Laravel 13 support, plus a type declaration on the Search component's $q property. Treat it as a routine minor upgrade. The one thing to check before bumping is any local subclass or override of the Search component that assigns a non-string to $q; that will now error. Otherwise, this release de-risks our framework upgrade path and requires no product-side work.