- Can I install fungio/dataexporter-bundle in a Laravel application?
- No, not as a package install. It is a Symfony bundle, and bundles are registered through the Symfony Kernel via bundles.php and DependencyInjection extension classes, a mechanism Laravel does not have. To use it in Laravel you would have to vendor the exporter classes, bind the exporter factory in your own service provider, and rebuild the configuration in a config/dataexporter.php file. That discards most of what the bundle actually ships, which is its Symfony integration layer.
- What is fungio/dataexporter-bundle used for?
- It exports data to CSV, Excel, XML, HTML, and JSON by letting you define exporters, map columns, and generate downloadable files from arrays or Doctrine queries. It is aimed at report generation and admin panels inside a full Symfony application. The package is a fork of EEDataExporterBundle, so its API and design lineage trace back to that project.
- How do I install fungio/dataexporter-bundle with Composer?
- On Symfony you would run composer require fungio/dataexporter-bundle, register the bundle in AppKernel or config/bundles.php, and supply the bundle configuration. Before installing, read composer.json to confirm the PHP constraint, the supported Symfony versions, and which spreadsheet library the Excel writer depends on. The README excerpt is thin, so treat the repository itself as the real documentation.
- Which Symfony versions does fungio/dataexporter-bundle support?
- The bundle was built for the Symfony 3.x and 4.x era, where autowiring your own service definitions was the normal workflow. There is no evidence that its DependencyInjection extension is compatible with Symfony 6 or 7 component signatures. Verify this with a scratch install before assuming it works on a modern Symfony release.
- Does fungio/dataexporter-bundle support PHP 8?
- This is unverified. The metadata shows no PHP 8.x claim and no visible CI matrix, and the package has zero dependents, so there is no external signal that the code runs on current PHP. Run a one-day compatibility spike on your target PHP version and treat a hard failure on PHP 8 as a stop signal rather than something to patch around.
- Does the Excel export require PHPExcel?
- That is the main technical risk and it must be checked in composer.json. Older Symfony-era export bundles commonly depend on PHPExcel, which was abandoned in 2019 and is incompatible with PHP 7.3 and later. If the writer is backed by phpoffice/phpspreadsheet instead, still verify the version constraint against your PHP and framework versions.
- What are the best Laravel alternatives for exporting data to CSV and Excel?
- Every export format this bundle offers is commodity functionality already covered by maintained, Laravel-native libraries. Look at maatwebsite/excel for Excel, league/csv or spatie/simple-excel for CSV, and PhpSpreadsheet directly for low-level spreadsheet control. Choosing one of these removes an abandoned or unverified dependency from your supply chain at no capability cost.
- How would I configure exporters in a Laravel app if I vendor this bundle?
- You cannot reuse the bundle's Symfony YAML configuration, so you would re-implement it as config/dataexporter.php and bind the exporter factory manually in a service provider. Budget roughly half a day for that scaffolding plus discovery work, before any format-specific problems surface. Isolate the vendored code behind your own interface so it can be swapped out later without touching call sites.
- Is fungio/dataexporter-bundle safe to use in production?
- The signal is weak: four stars, zero dependents, and a single fork with no visible maintainer activity. Check the last commit date and tag, and confirm the license permits vendoring the code into your codebase. Also treat the HTML export target with caution, since templating and escaping features rarely survive a security review intact.
- When is fungio/dataexporter-bundle still a reasonable choice?
- It fits a legacy Symfony 3.x or 4.x application that uses the full framework and autowires its own services, and only for the export formats whose underlying writers are still maintained. In that setting it is adequate. For Laravel 8, 9, 10, or 11 projects it is a rewrite-and-vendor exercise rather than an integration, so use it as a capability reference and implement the export contract against a supported library instead.