Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Excel Bundle

Excel Bundle Laravel Package

moveek/excel-bundle

Moveek Excel Bundle simplifies Excel import and export in Laravel/PHP apps, offering a lightweight wrapper for reading spreadsheets and generating downloadable files. Configure sheets, mappings, and formatting, then integrate exports and imports into controllers or jobs with minimal code.

View on GitHub
Deep Wiki
Context7

Symfony bundle to integrate phpoffice/phpspreadsheet library (https://github.com/PHPOffice/PhpSpreadsheet)

Frequently asked questions about Excel Bundle
Is moveek/excel-bundle a Laravel package or a Symfony bundle?
Despite being described as a Laravel/PHP package, moveek/excel-bundle is a thin Symfony service-provider bundle around phpoffice/phpspreadsheet. The repository uses bundle registration and a Symfony config tree, not a Laravel service provider. That matters because Laravel will not auto-discover or register it the way it does Laravel packages. Treat the Laravel positioning as marketing copy and verify composer.json and the bundle class before adopting it.
How do I install moveek/excel-bundle in a Laravel application?
You can try composer require moveek/excel-bundle, but installation alone does not give you Laravel integration. There is no documented Laravel service provider, facade, or auto-discovery path, so you would either bridge Symfony bundle semantics or instantiate services manually and bypass the config layer. At that point the bundle adds little beyond PhpSpreadsheet. For a Laravel app, install phpoffice/phpspreadsheet directly or use maatwebsite/excel instead.
Does moveek/excel-bundle support XLSX and CSV import and export?
The package advertises XLSX and CSV support because it wraps PhpSpreadsheet, which handles those formats. The bundle itself mainly adds container wiring and configuration for temp directories, caching, and reader/writer factories. Any format support ultimately depends on the PhpSpreadsheet version allowed by the bundle's composer constraints. Check those constraints before assuming current XLSX or CSV behavior.
Can I map spreadsheet rows to Eloquent models with moveek/excel-bundle?
The overview mentions simple row mapping to arrays or models, but the assessment found no import/export domain model and no Eloquent-specific integration. Basic row-to-array mapping may exist as a thin helper over PhpSpreadsheet, but you should not expect Laravel model hydration, validation, or relationship handling. For Eloquent imports, maatwebsite/excel provides a more complete, Laravel-native mapping layer. If you need custom mapping, write it against PhpSpreadsheet directly.
Does moveek/excel-bundle work with Laravel 10, 11, or 12?
There is no evidence of Laravel version support because the package is built as a Symfony bundle, not a Laravel package. Its composer.json will declare PHP and Symfony constraints, not Laravel framework constraints, so Laravel 10, 11, or 12 compatibility is not guaranteed. You would need to test installation in an isolated Laravel app and inspect dependency resolution. Given the architecture mismatch, a Laravel-native alternative is the safer choice.
How does moveek/excel-bundle compare to maatwebsite/excel?
maatwebsite/excel is Laravel-native and solves the hard parts: chunked reads, queued imports, export responses, and model mapping. moveek/excel-bundle is a thin Symfony bundle around PhpSpreadsheet that mainly adds config and container wiring. It has no documented queue integration, chunking, or streaming iterator. For most Laravel teams, maatwebsite/excel or direct PhpSpreadsheet is the better fit.
Is moveek/excel-bundle safe for production use with uploaded spreadsheets?
The assessment flags high supply-chain risk: zero stars, zero dependents, a single maintainer, and no visible release history. PhpSpreadsheet parses untrusted XML, ZIP, and shared-string content and has a real CVE history, so an unaudited shim in front of it can complicate your patch path. If the bundle pins PhpSpreadsheet narrowly, you may be blocked from upstream security fixes. The recommendation is not to adopt it for production without a full audit and a fork plan.
Does moveek/excel-bundle support queued imports, chunking, or streaming large files?
No such capabilities are documented or evident from the assessment. The bundle is described as container wiring plus a config tree for temp directories, caching, and reader/writer factories, with no queue integration, chunked read iterator, or streaming response builder. PhpSpreadsheet itself can be used with chunked reading and cell caching, but you would implement that logic yourself. For large files in Laravel, use maatwebsite/excel or build a dedicated PhpSpreadsheet service.
How do I format headers and column widths with moveek/excel-bundle?
The package advertises styling helpers for headers, column widths, and basic formatting, but these are likely thin passthroughs to PhpSpreadsheet. You would still need to understand PhpSpreadsheet's worksheet and style APIs to do anything beyond the basics. Because the bundle is unaudited and lightly maintained, verify the helper methods in source before relying on them. For complex formatting, use PhpSpreadsheet directly so your styling code is not dependent on an unmaintained wrapper.
Is moveek/excel-bundle maintained, and should I fork it or use PhpSpreadsheet directly?
There is no visible release history, CHANGELOG, or community around the package, and the assessment describes a single maintainer with zero dependents. MIT licensing means forking is legally straightforward, but the best case is that the bundle saves you a small config file and the worst case is an emergency fork under incident pressure. The recommended path is PhpSpreadsheet directly behind your own reader/writer interfaces, or maatwebsite/excel for Laravel-native features. Fork only if an audit finds non-obvious logic worth keeping.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
abbasudo/artisan-route
mirvan/ippanel
ignibyte/aic-framework
glavweb/data-schema-bundle
glavweb/datagrid-bundle
tacticmedia/scim-server
uni-method/frame
neika-ai/sdk
adachsoft/php-code-style
pharaonic/laravel-notification-dependencies
beautinow/translug
dev-brainiac/bot-cloaked
octoberrain/html
octoberrain/extension
octoberrain/exception
octoberrain/contracts
adachsoft/api-version-bundle
cgv/localized-resource
noith/settings
kda/laravel-package