- How do I install 3x1io/filament-excel in a Laravel application?
- Install it with Composer using composer require 3x1io/filament-excel. The package is a Filament panel plugin with an auto-discovered service provider, so you can optionally publish its config and assets, then register the export action on a target Resource or table. Most developers should have a first export working in under a day. The real effort is in guardrails such as disk targets, file retention, queueing, and column mapping rather than installation.
- Which Filament and Laravel versions does filament-excel support?
- The package assumes a Filament-based admin panel on Laravel 10/11-era and PHP 8.1 or newer, but you should verify the exact constraints in its composer.json against your locked versions before committing. Filament plugins frequently pin narrow version ranges, and a Filament major bump has historically forced plugin rewrites. There is no stated support window in the available documentation, so budget for upgrades accordingly.
- Does filament-excel support queued exports for large datasets?
- Yes, the package advertises queued processing as part of its export workflow. You should still confirm whether exports are streamed or buffered in memory, because large spreadsheets are the classic cause of memory limit and request timeout failures. Test with realistic row counts and configure your queue workers and timeouts before relying on it in production.
- Where does filament-excel write exported files, and are they access controlled?
- Exports write real records to disk, and the default disk target is not documented in the available material, so check the package config and set it explicitly. Use a private disk with access controls rather than a public one, and add retention or cleanup jobs for generated files. Misconfigured disks or missing cleanup are a PII and data leak risk, not just housekeeping.
- Does filament-excel respect Filament resource policies and row-level scoping?
- The plugin inherits Filament's action and policy model, so authorization should continue to flow through your existing Resource policies and canExport-style gates. That is good for least-privilege alignment, but verify it rather than assume it. Specifically test whether a user can export rows they are not allowed to view.
- Can I customize which columns and formats are exported?
- Yes, the package supports customizable columns for exports. Plan your column and format mapping around what downstream consumers need, including date formats and encoding. When replacing bespoke export code, run both paths in parallel for one reporting cycle and diff the outputs before retiring the old one.
- Is filament-excel production ready at version 1.0.1?
- Treat it as early-stage, single-maintainer-dependent code. Version 1.0.1 is a narrow patch fixing inflection of irregular plurals in derived names, with a very small contributor base and one external contributor in that release. The fix shows someone is triaging correctness bugs, but it also suggests thin automated coverage, so confirm CI and tests exist in the repository before depending on it.
- Will upgrading to v1.0.1 break my existing exports or downstream jobs?
- There are no API changes, deprecations, or migration steps, so code-level upgrade risk is effectively nil. The patch corrects irregular plural inflection, likely in export file names, sheet titles, or model labels. That cosmetic difference can break downstream jobs that key on file names, so review naming for the locales you use before deploying.
- How should I test filament-excel exports before deploying to production?
- Register the export action on a single Resource first and validate the output shape against an existing manual or spreadsheet workflow. Then check permissions with a non-admin user, verify the disk target is private, and confirm retention cleanup runs. For large datasets, test queue behaviour, memory usage, and timeouts under realistic row counts.
- What are alternatives to filament-excel for exporting data in Laravel?
- If your admin stack is already Filament, this plugin adds exports with low ceremony. If exports must be triggered from APIs, scheduled jobs, or non-Filament surfaces, a thin in-house exporter or direct use of Laravel-Excel and PhpSpreadsheet is usually a better fit. Avoid pulling in a UI-coupled plugin for non-UI export needs, since it would be dead weight.