Laravel Query Enrich Laravel Package

Product Decisions This Supports

• Feature delivery: Still a tactical accelerator for filter-heavy Laravel features (admin dashboards, search endpoints, reporting screens). The 1.4.0 release adds Enum support and isNull support in case->when, which better matches modern Laravel filtering patterns for status/type fields and nullable conditions, reducing custom query plumbing for common admin and reporting use cases.
• Build vs buy: Keep positioning as a low-cost “borrow” dependency rather than a platform bet. MIT license and small integration surface still make it cheap to trial. The release shows active maintenance and Laravel 13.x compatibility, which improves lifecycle fit, but low ecosystem adoption still argues for isolation behind an internal wrapper or fork if usage expands.
• Roadmap: Can unblock MVP/internal-tool milestones and now aligns better with apps planning a Laravel 13 upgrade. Do not let it shape core architecture; maintain a replace/exit path. The SQLite exists fix and subquery/DBFunction fix reduce edge-case risk for reporting and local/test environments.
• Use cases: Internal back-office tools, CRUD filtering, ad-hoc reporting, prototypes, enum-backed filters, nullable-condition filtering, and Laravel apps where common query enrichments (conditional clauses, date filters, search helpers) recur. Less attractive for customer-facing scale or compliance-heavy workloads.

When to Consider This Package

• Consider it when: your team is Laravel-native, the need is commodity query ergonomics, the application is internal or low-risk, and you can pin the version, add tests, and vendor/fork if necessary. It is a stronger fit when your roadmap includes Laravel 13 or you need enum-backed filters and nullable case->when handling without custom macros.
• Look elsewhere when: the workload is customer-facing at scale, security/compliance requirements are strict, you need a supported library with SLA or broad community backing, or you need serious query-filtering features (e.g., Spatie Query Builder). Also skip it if the helpers are trivial enough to implement in-house in a few hours, or if you require a dependency with substantial adoption and long-term ecosystem certainty.

How to Pitch It (Stakeholders)

• Executives: A low-cost Laravel productivity helper that can shorten delivery of internal tools and reporting features. The 1.4.0 release adds practical enum/nullable-filter support and Laravel 13 compatibility, signaling active maintenance. MIT-licensed and easy to trial, but still low adoption — pilot in a contained area rather than standardizing on it.
• Engineering: Drop-in query/Eloquent conveniences that cut boilerplate for common filtering patterns, now with enum support, isNull in case->when, subquery argument fixes, SQLite exists fixes, and Laravel 13 compatibility. Keep usage behind a thin internal abstraction, pin the version, cover it with tests, and avoid deep coupling so we can replace or fork it cheaply.