Weave Code
Report Bundle Laravel Package
gepur-it/report-bundle
A Symfony bundle for creating configurable reports from custom data providers and rendering results in multiple formats. It helps integrate reusable report generation into Symfony applications with flexible configuration and a simple report-building workflow.
Gepur ERP Report generation bundle
Frequently asked questions about Report Bundle
- Can I use gepur-it/report-bundle in a Laravel application?
- It is not a Laravel package; it is structured as a Symfony bundle with Symfony service configuration and dependency-injection assumptions. Direct installation into Laravel is likely to require a Symfony kernel or bridge and may create dependency conflicts. Treat it as a reference implementation rather than a drop-in Laravel dependency unless you verify a framework-agnostic core.
- Does gepur-it/report-bundle support Laravel 10 or Laravel 11?
- There is no evidence in the provided context that it supports Laravel 10 or 11. The package is a Symfony bundle last released in 2021 and appears targeted at Symfony, not Laravel service providers and Eloquent. Check its composer.json constraints and run a compatibility spike before assuming support.
- How do I install gepur-it/report-bundle with Composer?
- The normal Composer command would be composer require gepur-it/report-bundle, but installation into a Laravel app is not recommended without inspection. Review the repository composer.json for PHP, Symfony, Doctrine, and Twig constraints first. A failed dependency resolution or Symfony runtime requirement is likely in modern Laravel projects.
- What PHP and Symfony versions does gepur-it/report-bundle require?
- The provided context does not list exact PHP or Symfony version constraints. Because the last release was 2021-05-19, it may target older Symfony 4 or 5 and PHP 7.4 or 8.0-era runtimes. Inspect composer.json and test against your target PHP and Laravel versions before committing.
- Is gepur-it/report-bundle actively maintained?
- No, the context indicates it is effectively unmaintained: last release 2021-05-19, 2 stars, 0 dependents, and a score of 0.04. Adopting it means forking and owning compatibility, security patches, and support. That burden is rarely justified for a small Laravel reporting feature.
- What report formats does gepur-it/report-bundle support?
- The overview mentions configurable report output and multiple formats but does not enumerate HTML, PDF, Excel, CSV, dashboards, or scheduled reports. You must inspect the repository and documentation to confirm actual renderers and exporters. Do not assume PDF or Excel support without verifying dependencies such as Twig or spreadsheet libraries.
- Are there Laravel-native alternatives to gepur-it/report-bundle?
- Yes, Laravel teams should evaluate maintained Laravel-native reporting packages or build a small internal module using Eloquent queries, Blade or PDF rendering, and queued exports. The context recommends porting report concepts into Laravel services rather than installing the Symfony bundle. Compare maintenance, license, and Laravel version support before choosing.
- How do I test gepur-it/report-bundle in a Laravel project?
- Start with an isolated spike, not production installation: inspect composer.json, run Composer in a sandbox, and attempt only framework-agnostic report logic extraction. Write tests around your own report definitions, query layer, authorization, and export jobs. If the package requires a Symfony kernel, test it in a separate Symfony sandbox or service instead.
- Does gepur-it/report-bundle work with Doctrine and Eloquent?
- It is described as integrating with application/Doctrine data, which suggests Doctrine assumptions rather than Laravel Eloquent. The context does not confirm Eloquent support or a framework-agnostic data provider interface. You would likely need an adapter or a rewrite of the query layer for Laravel.
- What are the security concerns with gepur-it/report-bundle?
- Security posture, test coverage, license compatibility, and PHP 8.2/8.3 support are unknown and must be verified. If report definitions are user-configurable, SQL injection and authorization risks need review. An abandoned 2021 bundle also lacks ongoing security patches, so fork ownership and a security review are required.
Weaver
How can I help you explore Laravel packages today?