- How do I install and set up askdkc/livewire-csv in a Laravel app?
- Install it with composer require askdkc/livewire-csv, then run php artisan livecsv-setup, which publishes the config file and migration and optionally runs the migration for you. After that, add the HasCsvImports trait to the model you want to import into. You also need the queue tables and a running queue worker, because imports are processed as queued jobs.
- Which Laravel and Livewire versions does livewire-csv support?
- The README does not publish a supported Laravel or Livewire version matrix, so check the composer.json constraints on Packagist before committing. The repository runs its own GitHub Actions test workflow and has picked up PHP 8.3 support and a League CSV 9.12 fix through its changelog. Because the package ships Livewire components, verify behavior against the Livewire major version in your app during a short spike, especially if you are on Livewire 3 or 4.
- Do I need a queue worker to import CSV files with this package?
- Yes. The package is queue-dependent by design, reading large CSV and TSV files with PHP generators and writing to the database from a queued job. You need the queue:table and queue:batches-table migrations in place and at least one worker running, or imports will be dispatched and never finish. Size your worker memory and timeout settings around the files you expect to upload.
- How does livewire-csv handle updating existing records instead of duplicating them?
- It uses database UPSERT statements, so each row creates or updates a record rather than simply appending. By default the upsert column is id, and overriding the upsert-columns option requires a real primary key or unique index, which the README demonstrates with a unique(['name', 'email']) migration. If your table has no clean natural key you will need migration work first, and changing a primary key is fairly invasive.
- Can I import CSV data into any Eloquent model, or only the User model?
- The trait can be added to models other than User, and the README uses User mainly as a demonstration. The real constraints are that the upsert columns must map to a primary or unique index and that the CSV headers line up with your model attributes. Note that the package does not document per-model or per-tenant authorization on the component, so you are responsible for restricting who can reach the importer.
- Does livewire-csv support TSV files and custom delimiters?
- Yes, TSV is supported alongside CSV, and the config exposes file_type and set_delimiter options. The configuration surface is deliberately small, covering layout, file_type, set_delimiter, and file_upload_size, so unusual encodings or formats may need pre-processing. Test a real sample file with your intended delimiter before relying on it.
- How do I customize the CSV importer UI, and is Tailwind CSS required?
- The layout config option only supports tailwindcss, so a Tailwind or TALL stack app gets the component working quickly after publishing the views. On a non-Tailwind design system you can fall back to the @csvStyles and @csvScripts directives and accept the vendor markup, or publish and fork the Blade views under the MIT license. That is acceptable for an internal admin screen but awkward for a brand-sensitive customer-facing UI.
- How do I test Livewire CSV imports in my Laravel test suite?
- Because the importer is a Livewire component, you can drive it with Livewire's testing helpers while using Storage::fake and Queue::fake to assert an upload dispatches the expected job. Assert the resulting rows with assertDatabaseHas rather than checking the UI, since the package does not document row-level error reporting. Always add a case where a row already exists so you exercise the upsert path and catch unique index problems.
- Is livewire-csv safe to use in production for large files and malformed rows?
- It is reasonable for internal admin imports, but treat it as a small single-maintainer package with modest adoption and no dependents, meaning you own the edge cases. The README does not document per-row validation errors, partial upload failure semantics, or rollback behavior, and because it upserts, a malformed row can update an existing record instead of failing loudly. Validate and normalize files before importing, take backups, and test at your real file size and memory limits with the default 100 MB upload setting in mind.
- Can I trigger CSV imports from an API endpoint, CLI command, or scheduled job instead of a Livewire view?
- No. The package's entry points are a Livewire component and an Alpine-backed Blade button, so API, CLI, scheduler, and Inertia, Vue, or React front ends have no headless entry point. For those cases, use league/csv or Laravel Excel inside your own queued job instead. Choose this package when the import screen genuinely belongs in a Blade and Livewire application.