- What is eightynine/filament-excel-import used for?
- It is a Filament plugin for importing Excel and CSV files into Laravel admin panels. You upload a spreadsheet, map columns to model fields, validate rows, and run the import from a Filament resource. It is best suited to internal ops, finance, catalog, or user-admin imports rather than customer-facing ingestion or high-volume ETL.
- How do I install eightynine/filament-excel-import in a Laravel Filament app?
- Install it with Composer and rely on Laravel package auto-discovery for the service provider. Then publish any config or assets and attach the import action to a Filament resource. Confirm the package's Composer constraints against your Filament, Laravel, and PHP versions before committing.
- Does this package support Filament v4 and Laravel 12?
- The available context does not confirm Filament v4 or Laravel 12 support, so verify it in the package composer.json and with composer why-not against your target versions. The technical assessment specifically flags checking Filament v3 versus v4 and Laravel 10, 11, or 12 support. Pin to a known-good minor version and test upgrades in a branch.
- Does eightynine/filament-excel-import use maatwebsite/excel or PhpSpreadsheet?
- It likely depends on a spreadsheet parsing library such as PhpSpreadsheet or Laravel Excel, but the exact dependency chain should be checked in composer.json. That dependency matters because file-parsing libraries introduce security, memory, and upgrade considerations. Review transitive constraints before adopting it in production.
- Can it handle large Excel imports without running out of memory?
- The package is described as handling large imports through a configurable workflow, but the assessment warns that memory pressure depends on whether it loads the full file or supports queued or chunked imports. Run a spike with representative row counts and timeouts before relying on it for high-volume files. If needed, add queue processing, chunking, or row caps behind the plugin.
- How are partial failures and validation errors handled during an import?
- The package supports row validation, but the exact failure behavior, such as transaction rollback, error reporting, or silent skipping, should be confirmed in the package documentation and a sandbox test. Define duplicate handling and rollback expectations before piloting on real data. Treat the import as a UI accelerator and keep an internal importer contract for business logic.
- Can I customize column mapping, value transforms, and per-row validation?
- The plugin's workflow includes mapping spreadsheet columns to model fields and validating rows, and the assessment lists custom importers, transformations, and per-row validation as key questions to verify. Real implementation effort goes into column contracts, validation rules, transforms, and duplicate handling, not installation. Test these behaviors with malformed headers, dates, Unicode, and duplicates.
- Can I restrict who can run imports in Filament?
- Filament actions can typically be authorized or hidden per role, but you should confirm how this plugin's import action integrates with Filament's authorization APIs. Also check that uploaded files are isolated by tenant or disk if you handle sensitive data. The assessment flags role-based visibility and file isolation as important production questions.
- Is eightynine/filament-excel-import safe and production-ready?
- It is MIT licensed and small, with moderate-low technical risk, but it has limited production evidence at roughly 95 stars and zero dependents. Single-maintainer risk and spreadsheet-parser CVEs are real concerns. Pilot it behind a feature flag on one low-risk resource, keep a CSV or Excel fallback, and budget ongoing maintenance for dependency and Filament upgrades.
- What should I use instead of this plugin for high-volume or customer-facing imports?
- For customer-facing ingestion or high-volume ETL, use a dedicated importer or queue pipeline rather than a Filament admin plugin. In a non-Filament Laravel app, Laravel Excel plus a thin custom UI is a better fit. Do not add Filament solely to get import functionality.