Lampager Laravel Laravel Package

Product Decisions This Supports

• Pagination strategy (offset vs. keyset/seek): Lampager generates cursor-based (keyset) pagination queries, so it directly informs whether a feature should use OFFSET paging or cursor paging. This matters for feeds, activity streams, search results, and any list that must stay stable while rows are inserted or deleted.
• Bidirectional UX: It supports both "next" and "previous" cursors, which underpins infinite scroll, "Load more," and "Newer/Older" navigation without duplicating query logic per direction.
• Scale roadmap: Keyset pagination avoids the OFFSET N performance cliff on large tables, so adopting it is a scalability decision, not just a UI one.
• Build vs. buy: The alternative is hand-rolling cursor logic (ordering, tie-breaking, boundary/empty-page handling, reverse queries). This package replaces that custom code with a maintained dependency, reducing bespoke logic and its bug surface.
• Framework upgrade planning: v0.6.1 confirms PHP 8.5 support, Laravel 11+ test compatibility, documented Laravel 13 support, and permissive Laravel 14 constraints — useful input when deciding whether the package can survive an upcoming framework upgrade.

When to Consider This Package

Consider it when:

• You are on Laravel and use Eloquent or the Query Builder for the data you paginate.
• You need bidirectional cursor pagination with non-trivial ordering (multiple sort keys, nullable columns, custom tie-breakers).
• You have large or fast-changing tables where offset paging causes slow queries or duplicated/skipped rows.
• You want the pagination behavior to be covered by a dependency rather than maintained in-house, and you value a package that is actively tracking new PHP/Laravel releases.

Look elsewhere when:

• Your UI is page-numbered with "Page 3 of 47" and total counts — that is offset pagination's job, and Laravel's built-in paginate()/cursorPaginate() already covers simple cases.
• You are not on Laravel, or you paginate data that does not come from a query builder.
• You require a formal support SLA or a vendor-backed dependency rather than a single-maintainer open-source package.
• The pre-1.0 version number is a blocker for your release/compliance process.

Note that v0.6.1 is a maintenance and compatibility release: it contains no new features, no breaking changes, and no deprecations. Its significance is support-matrix signaling (PHP 8.5, Laravel 11+ tests, Laravel 13 docs, Laravel 14 allowed), which reduces upgrade risk but does not change the product fit.

How to Pitch It (Stakeholders)

For executives (one paragraph): Lampager is a small, focused library that makes list-based features — feeds, search results, activity logs — load reliably and cheaply at scale. It replaces custom pagination code we would otherwise write and maintain ourselves, and the new release shows the maintainer is keeping pace with PHP 8.5 and Laravel 11 through 14, which lowers the risk of it blocking a future framework upgrade. It is a pre-1.0, single-maintainer open-source dependency, so the decision is low-cost to adopt and low-cost to reverse, but it should not be treated as vendor-supported infrastructure.

For engineering: Adopt via Composer; it integrates with existing query builders rather than replacing them. v0.6.1 is a compatibility-only release — PHP 8.5 support, ResourceTest fixes for Laravel 11+, Laravel 13 documentation, and a permissive Laravel 14 constraint — with no API changes, so upgrading from v0.6.0 carries no migration work. Where requirements are simple (single-direction, page-numbered lists), prefer Laravel's native pagination and skip the dependency; where ordering is complex or bidirectional cursors are required, this package removes a meaningful amount of hand-written edge-case handling.