Weave Code
Grid Laravel Package
prezent/grid
A Laravel package for building data grids and tables in PHP. Define columns and rows, control formatting and rendering, and display structured, searchable data in your Blade views with minimal configuration and reusable, customizable grid classes.
Generic data grids and list
Frequently asked questions about Grid
- What is prezent/grid and what is it used for in Laravel?
- prezent/grid is a Laravel package for building server-side data grids and tables in PHP. You define columns and rows in reusable grid classes, control formatting and rendering, and output structured, searchable tables in Blade views with minimal configuration. It targets the classic back-office or admin table problem rather than being a general-purpose UI toolkit.
- How do I install prezent/grid with Composer?
- Install it with composer require prezent/grid; Laravel package auto-discovery registers the service provider automatically. From there you publish the config and views with the vendor:publish command and begin defining your grid classes. For a conventional Laravel app the initial wiring is a matter of hours rather than weeks.
- Which Laravel and PHP versions does prezent/grid support?
- The package does not publish a broad compatibility matrix, so read the constraints in its composer.json and check them against your Laravel LTS and PHP version before adopting it. There is no visible release cadence or CI pipeline, so each Laravel major upgrade is a potential breaking change with no guarantee of a timely upstream patch. Pin the version explicitly and plan to maintain a fork if you rely on it long term.
- Is prezent/grid server-side rendered, or does it need Vue, React, or Inertia?
- It is server-rendered: grids are defined in PHP and rendered to HTML inside Blade views. That makes it a good fit for classic Laravel plus Blade applications and a poor fit for API-first, Inertia, React, or Vue frontends, where grid logic belongs in the frontend layer. It is an opinionated single-purpose component, not a framework.
- Does prezent/grid handle sorting, filtering, and pagination on large datasets?
- Sorting, filtering, and pagination are part of the package's stated scope, and it is designed around server-side data sourcing rather than client-side table rendering. What is not documented is how COUNT queries, large offsets, and chunked datasets are handled, so validate those on a spike using your real row counts. For tables in the tens of thousands of rows, benchmark performance before committing.
- Can I use Eloquent relations, the query builder, or API data sources with prezent/grid?
- It is aimed at conventional Laravel data sources such as Eloquent models and the query builder. Relation columns and eager-load handling are not clearly documented, so confirm them in the source or in an isolated spike before assuming your schema works. Remote API or non-relational data sources are not a documented fit.
- Does prezent/grid support CSV or Excel export, bulk actions, or per-column authorization?
- The package overview does not document export support, bulk actions, or row-level and per-column authorization hooks. Those admin concerns would fall back to your application layer, which is a meaningful amount of additional work. If they are hard requirements, budget for building them yourself or choose a more feature-complete admin package.
- Does prezent/grid work with Tailwind or Bootstrap, and can I publish and override the views?
- The package is designed to sit on top of a Bootstrap or Tailwind-style CSS layer, and its config and views are publishable so you can override the markup. Published view overrides live in your repository and can silently conflict with upstream changes on upgrade, so diff them each time you bump the package. Check whether you get styled or unstyled markup out of the box before planning design work.
- Is prezent/grid actively maintained and safe to use in production?
- Treat it as unproven: roughly 14 GitHub stars, zero dependents, and no visible CI, security disclosure path, or named maintainer with SLAs. It is MIT licensed and narrow in scope, which limits architectural blast radius, but you would be the first meaningful adopter and may end up owning the dependency. Server-rendered output keeps the attack surface small, but confirm cell output is escaped by default and that any raw-HTML cell renderer is explicit and limited to trusted values. Also validate filter input before it reaches the query builder to avoid injection or denial-of-service issues.
- How does prezent/grid compare to Filament, Livewire Tables, or DataTables?
- It overlaps heavily with Filament, Orchid, Livewire Tables, and DataTables, but with far less community support and no ecosystem of plugins or answers to lean on. If your stack already includes one of those, prezent/grid duplicates capability rather than adding it. It is only worth considering for a plain Laravel plus Blade application that wants a lightweight, PHP-defined grid and can absorb the maintenance risk.
Weaver
How can I help you explore Laravel packages today?