Weave Code
Data Grid Export Laravel Package
cartalyst/data-grid-export
A Laravel package for exporting Cartalyst Data Grid results, helping turn filtered grid data into downloadable files for reporting, analysis, and sharing. It integrates with existing data grids to simplify export workflows for developers and admins.
HTML markup templating on the client side, simple API on the server side. Incredibly simple and easy to use.
Frequently asked questions about Data Grid Export
- How do I install cartalyst/data-grid-export in a Laravel app?
- Install it with Composer using composer require cartalyst/data-grid-export. Because the repository's composer.json is not available in the provided evidence, verify the required PHP and illuminate/* version constraints before installing. In a Laravel app, confirm service provider discovery or register the provider manually if the package version predates discovery. Then publish any package configuration if the source includes it.
- Which Laravel versions does cartalyst/data-grid-export support?
- The latest known tag is v4.1.0 from December 2020, which places it in the Laravel 8.x era. There is no evidence in the provided material of Laravel 9 or Laravel 10 support. Check the package's illuminate/support constraint in composer.json; if it is pinned to ^8.0, Composer will block installation on newer Laravel versions regardless of PHP support.
- Does cartalyst/data-grid-export support PHP 8, 8.1, 8.2, or 8.3?
- Yes, v4.1.0 is a one-line release adding PHP 8 support. Because it shipped on 2020-12-23, that support refers to PHP 8.0 only; PHP 8.1, 8.2, and 8.3 did not exist yet. The evidence does not show whether the constraint widened to ^7.4|^8.0 or was replaced with ^8.0 only, so verify this before relying on PHP 7.4 compatibility or modern PHP 8.x support.
- What file formats can I export from a Cartalyst Data Grid?
- The package is designed to export filtered Cartalyst Data Grid results as downloadable files for reporting, analysis, and sharing. The provided overview does not enumerate specific file formats or export writers. Inspect the package source or documentation for the available export configuration, and test the exact format your application needs.
- Is cartalyst/data-grid-export still maintained?
- Treat maintenance status as unconfirmed. The newest known release is v4.1.0 from 2020-12-23, and the evidence base lacks post-4.1.0 release history, a changelog, or a CI matrix. A four-week turnaround on PHP 8.0 GA is a positive responsiveness signal for that release, but it does not certify ongoing maintenance through PHP 8.1, 8.2, or 8.3.
- Can I use cartalyst/data-grid-export with Laravel 9 or Laravel 10?
- Not without verification. A package whose newest tag is v4.1.0 from December 2020 may carry illuminate constraints that block Laravel 9 or 10, and it does not certify newer PHP runtimes. Try installing it in a disposable branch, confirm the resolved illuminate/* and PHP constraints, and run your export tests before committing to it.
- How does cartalyst/data-grid-export integrate with an existing Data Grid?
- The package provides a simple server-side API and client-side HTML markup templating for exports. You connect it to an existing Cartalyst Data Grid so that the current filtered results become the export payload. Keep the export action aligned with the same filters and authorization rules as the grid itself.
- How should I test cartalyst/data-grid-export before using it in production?
- Write feature tests that build a small grid dataset, trigger an export, and assert the downloaded file's contents and headers. Add a larger dataset test to check memory and execution time, because export code can stream or buffer depending on implementation. Run the suite on the exact PHP and Laravel versions you plan to deploy.
- What are the alternatives to cartalyst/data-grid-export?
- If you need a maintained export layer for modern Laravel, alternatives include Maatwebsite/Laravel Excel, league/csv, or a small custom exporter built around your grid queries. This package is specifically useful when you are already using Cartalyst Data Grid and want its filtered results exported with minimal glue. For legacy Laravel 8 applications, it may still fit if its constraints resolve cleanly.
- What production risks should I check with cartalyst/data-grid-export?
- The main risks are currency and runtime coverage: the last known release is from 2020, so it does not certify PHP 8.1+ deprecations, PHP 8.2 readonly semantics, or PHP 8.3 typed constants. There is also integration risk if illuminate/* constraints block modern Laravel, plus operational concerns such as memory use on large grids and access control for downloaded reports. Pin the package version, audit its manifest, and test on your target base image before production.
Weaver
How can I help you explore Laravel packages today?