- Does alperenersoy/filament-export support Filament v4?
- The package hooks directly into Filament's table and action internals, and Filament ships breaking changes between major versions, so a build that works on v3 is not guaranteed to work on v4. There is no confirmed compatibility matrix in the available material, so treat v4 support as unverified. Inspect the composer.json constraints and the latest release tags before upgrading your panel.
- How do I install filament-export in a Laravel application?
- Require the package with Composer, register the plugin in your Filament PanelProvider, and optionally publish the config and Blade views. Then attach the export action and the bulk export action to the tables or resources you want to expose. A competent Filament developer should get a working pilot on one resource within one to two days.
- Is filament-export safe to use in production on large tables?
- Exports in this class of package typically execute the query and build the file in memory inside the request cycle, which on wide tables with joins risks memory exhaustion and gateway timeouts. Validate behavior against production-sized data before rollout, and confirm whether your installed version offers a chunked or streamed mode. If it does not, plan mitigation such as narrowing columns or moving the work off the request.
- Does filament-export respect Filament policies and tenant scoping when exporting?
- This is the most important thing to verify yourself before shipping. Determine whether the export reuses the resource's getEloquentQuery() and therefore inherits row-level scoping, tenancy, and model policies, or whether it re-queries the table independently. A bulk export that bypasses policy scoping is a data-leak vector, and every export drops a copy of production data on an end-user device with no audit trail.
- Can I customize which columns are exported and the output filename in filament-export?
- Yes, the action is designed for configurable exports: you control the column set, the filename, and the output format such as CSV or Excel from the admin panel. The exact method names depend on the installed version, so check the published config and the action signature. This is also where you match header labels and date or currency formatting to your existing reports.
- Does filament-export produce PDFs, or is the print feature browser-based?
- The package advertises both export and print functionality, and print output is typically rendered through Blade views. Whether a given setup produces a true server-side PDF or triggers the browser's print dialog on a Blade view depends on your configuration and the PDF dependency you install. Server-side rendering costs more but is the only option with any fidelity guarantee.
- What are the hard dependencies of filament-export, and does it need a system binary?
- Expect a spreadsheet writer such as maatwebsite/excel for XLSX and a PDF engine such as dompdf if you enable PDF output. Some PDF engines, notably wkhtmltopdf, require a system binary that must be installed on every host. The available README excerpt does not confirm the exact list, so read composer.json and check required PHP extensions before installing in a locked-down environment.
- Is filament-export actively maintained, or should I plan to fork it?
- It is a single-maintainer package with around 275 stars and zero dependents in the index, which is a weak adoption signal relative to its star count and suggests launch-driven attention rather than sustained production use. Assume you may need to fork it if a Filament upgrade lands before the package catches up. Review commit and issue activity over the last 12 months, and treat the listed release dates as unverified until you check tags directly.
- Can filament-export run exports on a queue or in chunks?
- There is no evidence in the available material of a queued or chunked export path, and the default pattern for this kind of Filament action is a synchronous build-and-stream within the request. If you need queued jobs, progress reporting, or large-volume chunking, plan to wrap the export logic yourself or use a dedicated export package. Confirm this before designing around the action for nightly or scheduled extracts.
- What are the alternatives to filament-export for customer-facing or non-Filament apps?
- If your admin surface is not built on Filament, stop here, because this is a panel plugin with no partial-adoption path. It is also a poor fit as a customer-facing export or reporting mechanism, since the abstraction is a UI action rather than a data pipeline with scheduling, delivery, and downstream contracts. For those cases use a dedicated export or reporting library and keep filament-export for internal back-office extracts.