Weave Code
Csv Laravel Package
portphp/csv
CSV reader and writer for PortPHP import/export workflows. Stream CSV files with configurable delimiters, enclosures, and headers, and plug into PortPHP pipelines for efficient data migration, ETL, and bulk imports in PHP applications.
portphp/csv is a lightweight PHP package that brings CSV reading and writing to the PortPHP data import/export framework. It provides stream-based readers and writers that integrate seamlessly with PortPHP workflows, letting you transform CSV data through filters, converters, and other processing steps before writing results out.
- Configurable delimiter, enclosure, and escape characters
- Optional header row handling for both reading and writing
- Stream-based processing suitable for large files
- Works with PortPHP workflows, filters, and converters
Frequently asked questions about Csv
- Is portphp/csv a Laravel package with a service provider?
- No. portphp/csv is not Laravel-native; it is a thin adapter that supplies a CsvReader and CsvWriter to the Port ETL abstraction, formerly Ddeboer DataImport. It has no service provider, facade, publishable config, or Artisan command. You integrate it by writing your own glue code, ideally behind an internal service class or container binding.
- How do I install portphp/csv with Composer?
- Install it with Composer as a library dependency and pin the exact version in composer.json with a committed lockfile. Confirm the Port major version expected by the adapter, because namespace and API churn around the Ddeboer to Port rename is the most likely installation failure. Also verify your PHP version and mbstring or iconv extension assumptions in every target environment, including CI and container images.
- Which Laravel versions does portphp/csv support?
- portphp/csv does not declare Laravel support directly because it has no Laravel integration surface. Compatibility is determined by the package's PHP version constraint and its Port dependency, not by the Laravel framework version itself. Confirm the PHP runtime used by your Laravel version satisfies the Composer constraints, then test installation in CI before committing.
- How do I configure delimiter, enclosure, escape character, and headers for CSV import or export?
- The package exposes an options array covering delimiter, enclosure, escape character, encoding, and header row handling. Set these explicitly rather than relying on defaults, because CSV dialects vary and misconfiguration is a common source of corrupt imports. Wrap reader and writer construction in your own configuration so controllers, jobs, and tests do not depend directly on Port types.
- When should I use portphp/csv instead of League\Csv or Laravel Excel?
- Use portphp/csv when you are deliberately standardizing on Port as your ETL pipeline layer, with a Reader to Converter or Step chain to Writer flow. If your import features are built directly on Eloquent, League\Csv, or Laravel Excel, it adds an abstraction layer without removing work. Do not migrate working imports to Port for consistency alone; adopt it for a bounded use case first.
- Can portphp/csv handle large CSV files and streamed imports?
- The package is stream-based, but memory behavior depends on giving the reader a genuinely streamed source rather than an in-memory string or already-loaded file. For large files, process rows through the Port pipeline and drive the work from a queued job or console command. Test memory usage with realistic file sizes and confirm your source is streaming before relying on it in production.
- How do I report per-row validation errors during a CSV import with portphp/csv?
- Port provides pipeline structure but not a user interface or built-in per-row error reporting; that is your build. Register converters or steps that catch validation failures and record the row number and message, then persist or return those error rows to business users. Keep this error collection inside your own wrapper service so Port types stay out of controllers and jobs.
- What causes CSV import failures with BOM, encodings, quoted newlines, or malformed rows?
- The genuine functional risk lives in CSV edge cases rather than in the library: byte-order marks, non-UTF-8 input, delimiter, escape, or quote misconfiguration, header-to-field mapping drift, and malformed rows. Normalize encoding and strip BOM before parsing, and configure delimiter, enclosure, escape, and headers explicitly. Test with deliberately messy fixtures including quoted newlines and mixed encodings.
- How do I test a portphp/csv integration in a Laravel application?
- Wrap the package in an internal service such as CsvImportService that owns reader construction, converter registration, and error collection, then test through that interface rather than asserting against Port classes directly. Use fixtures with BOM, quoted newlines, mixed encodings, and delimiter variance, and assert both successful rows and collected error rows. Keep the exact package version pinned so tests remain stable across dependency updates.
- Is portphp/csv maintained, and what is the risk of depending on it?
- The code risk is low, but governance risk is moderate to high: 35 stars and an unverified repository imply an effectively single-maintainer bus factor with little community or security-review surface. The mitigating factor is decisive because the package is a thin wrapper over PHP native fgetcsv and fputcsv, so forking or replacing it is an hours-scale task rather than a migration project. Verify the tagged release date and maintainer of record, then pin the exact version.
Weaver
How can I help you explore Laravel packages today?