Weave Code
Laravel Resource Exporter Laravel Package
sinemacula/laravel-resource-exporter
A Laravel package for exporting resource collections and application data to downloadable files. It provides a clean, configurable API for choosing fields and formats, reducing repetitive boilerplate and making reports, admin exports, and data handoff workflows easier to build.
A Laravel package that provides flexible and extensible resource exporting capabilities, allowing you to easily convert JsonResource and JsonResourceCollection objects into various formats.
Frequently asked questions about Laravel Resource Exporter
- What does sinemacula/laravel-resource-exporter do in a Laravel app?
- It extends Laravel's JsonResource and ResourceCollection concepts into file-oriented exports, so existing API resource definitions can be reused for downloadable output. It sits in the presentation and serialisation layer and is aimed at reporting endpoints, admin download buttons, finance or BI hand-offs, and data-portability requests. Teams that have not adopted API Resources get less value because the package's leverage comes from reusing those definitions.
- How do I install sinemacula/laravel-resource-exporter?
- Install it with Composer using composer require sinemacula/laravel-resource-exporter; Laravel package discovery handles registration, and you can optionally publish the config. Then declare exporter classes alongside your existing resources. The assessment recommends pinning to ^3.1 and reading the 3.0.0 upgrade notes before writing exporters.
- Which Laravel versions does laravel-resource-exporter support?
- The 3.1.0 release added Laravel 13 support, and the best-fit stack in the assessment is Laravel 11, 12, or 13 on PHP 8.2+. The context does not confirm whether 3.1.0 widened the illuminate/* constraint or replaced it, so read composer.json at the 3.1.0 tag to see which majors are supported simultaneously. Support appears reactive rather than pre-release, so budget for a one- to two-quarter lag on future Laravel majors.
- Does laravel-resource-exporter support CSV, XLSX, JSON, and XML exports?
- The assessment uses CSV, XLSX, JSON, and XML as target deliverables for report and data handoff workflows, but it does not confirm which formats are supported out of the box. It also lists format-layer extensibility without forking as a key question. Verify the actual format list and extension points in the source or a short spike before committing.
- Can I export large resource collections without running out of memory?
- The provided assessment does not state whether large exports are streamed or chunked, or whether they are materialised in memory. That is explicitly listed as a key verification question, so test with representative data volumes and inspect the implementation before relying on it for large reports. The package also does not decide whether an export runs inline in a request or as a queued job.
- Should exports run inline in a controller or as a queued job?
- The package does not make that decision for you; the assessment calls it an application design choice. Inline request exports are simpler but may be unsuitable for large files or tight timeout limits, while queued jobs add infrastructure and operational concerns. Choose based on export size, user expectations, and whether a synchronous download is required.
- Is sinemacula/laravel-resource-exporter production-ready and well maintained?
- Maturity is provisional in the assessment because it is based on a single release note, not source review, test-coverage inspection, or download and adoption metrics. It flags single-maintainer risk, a bus factor of 1, and no assumed commercial support channel. Run a spike and review the repository before treating it as production-critical.
- What changed in version 3.0.0, and are there breaking changes?
- Version 3.x implies prior breaking changes, but the 2.x to 3.x boundary is unreviewed in the provided context. The assessment recommends reading the 3.0.0 upgrade notes before writing exporters and pinning to ^3.1. It does not list specific deprecated APIs or changes, so check the release notes and diff.
- How does laravel-resource-exporter compare with custom CSV or XLSX serialisers?
- The package is a convenience layer that saves writing format-specific serialisers by extending existing Laravel resource definitions. That saving compounds when you have several export surfaces, but teams without API Resources get less value. For a single bespoke export, custom code may be simpler; for multiple report endpoints, evaluate format coverage and extensibility first.
- What should I verify about tests, security, and licensing before adopting laravel-resource-exporter?
- The assessment lists the test matrix and CI coverage across PHP and Laravel versions as key questions, not confirmed facts. It also asks whether a documented security policy exists for reporting vulnerabilities. Separately, confirm the licence terms are compatible with your distribution model, whether SaaS or on-prem. Review the repository's CI configuration, tests, SECURITY file, and composer.json licence field before adoption.
Weaver
How can I help you explore Laravel packages today?