Weave Code
Advanced Export Laravel Package
filamentphp/advanced-export
Advanced export for Filament: export table data to Excel and CSV with configurable columns, formatting options, and a simple, customizable workflow. Integrates cleanly into Filament resources so you can ship polished exports with minimal setup.
filamentphp/advanced-export
Frequently asked questions about Advanced Export
- What is filamentphp/advanced-export used for?
- filamentphp/advanced-export is a Filament plugin for Laravel admin panels that adds Excel and CSV export workflows to table resources. It is designed for configurable columns, formatting options, and a simple customizable export flow. Use it as an accelerator for internal admin exports, not as a proven high-volume or compliance-grade export platform.
- How do I install and register filamentphp/advanced-export in a Laravel Filament app?
- Install it with Composer in a time-boxed spike branch and register the package's plugin or service provider in your Filament panel provider. Publish any config the package exposes, attach the export action to one low-risk resource, and validate the generated Excel and CSV files. No database migration is expected, which keeps the first integration low-risk.
- Which Filament, Laravel, and PHP versions does filamentphp/advanced-export support?
- The provided metadata does not list a confirmed Filament, Laravel, or PHP compatibility matrix. Check the Composer constraints and repository README before committing, then pin the exact package version you validate. Test against your current Filament major version because plugin APIs can break across upgrades.
- Can filamentphp/advanced-export handle large tables or queued exports?
- The available assessment flags synchronous exports as a scaling risk and does not confirm queued or chunked support. For large tables, verify memory usage, timeout behavior, and row limits in a sandbox before relying on it. Consider queueing, chunking, row caps, or a custom export job for high-volume data.
- Can I choose which columns and formatting options are included in Excel and CSV exports?
- Yes, the package is described as exporting Filament table data to Excel and CSV with configurable columns and formatting options. You can integrate the export workflow into Filament resources and tailor the output for standard admin use cases. Confirm the exact formatting features and writer behavior with representative test exports.
- Does filamentphp/advanced-export respect Filament table filters, hidden columns, and authorization policies?
- The package is positioned as an export action for Filament resources, but the available metadata does not document how table filters, hidden columns, relationships, or policies are enforced. Test exports with filtered tables, hidden fields, and users who have different permissions. Add your own authorization checks or an internal adapter if the package does not enforce them.
- Is filamentphp/advanced-export safe for exporting PII or regulated data?
- Treat it as an internal admin export accelerator, not a compliance-grade pipeline for sensitive data until maturity is proven. Review where files are stored, who can download them, retention behavior, and whether PII or regulated columns are included. Add access controls, redaction, and lifecycle policies before using it for sensitive exports.
- Does filamentphp/advanced-export protect against CSV formula injection and special characters?
- CSV formula injection is a real risk for any export feature, and the assessment explicitly calls it out as a concern. Escape or prefix dangerous leading characters and test payloads such as =, +, -, and @ in exported cells. Confirm the package's sanitization behavior or add a cleaning layer before production use.
- Is there a test suite, CI, and active maintenance for filamentphp/advanced-export?
- The metadata does not confirm a test suite, CI, or release cadence, and adoption signals are thin with 8 stars and 0 dependents noted in the assessment. Run your app's test suite plus export-specific checks for filters, hidden columns, permissions, special characters, large row counts, and CSV injection payloads. Assign an internal owner to track upstream releases and issues, and pin the version you validate.
- What are the alternatives or fallback options if filamentphp/advanced-export is abandoned?
- Keep a fallback custom export job or direct query export for critical paths, and wrap the package behind an internal adapter so it can be replaced without touching every resource. If the package stalls, fork it under an internal namespace or switch to a maintained export library. Expand usage only after output quality, performance, security, and maintainer responsiveness meet your gates.
Weaver
How can I help you explore Laravel packages today?