Weave Code
File Uploader Bundle Laravel Package
modera/file-uploader-bundle
Modera FileUploaderBundle is a Symfony bundle that handles file uploads within Modera-based applications, providing reusable upload handling for controllers and forms so files can be received, stored, and managed consistently across the Modera ecosystem.
[READ-ONLY] The bundle simplifies and introduces a consistent approach to uploading and storing uploaded files.
Frequently asked questions about File Uploader Bundle
- Is modera/file-uploader-bundle a Laravel package?
- No. It is a Symfony bundle built for Modera/Symfony applications and relies on Symfony DependencyInjection, HttpKernel, EventDispatcher, and bundle registration conventions. Laravel uses a different service container, HTTP kernel, middleware pipeline, and package discovery model, so it will not just work in a Laravel app.
- Can I install modera/file-uploader-bundle with Composer in Laravel?
- You can attempt composer require, but dependency resolution is likely to fail or force unwanted downgrades. The bundle targets Symfony 2.x/3.x-era components and older PHP versions that conflict with Laravel's illuminate packages. Any working setup would require a custom bridge rather than a standard Composer install.
- Does modera/file-uploader-bundle support Laravel 10 or Laravel 11?
- There is no official Laravel support. Its last release was in 2016, well before modern Laravel and PHP 8, and it is unlikely to be compatible with Laravel 10 or Laravel 11. Modern Laravel depends on Symfony 6/7 components, which this legacy bundle does not target.
- Is modera/file-uploader-bundle abandoned?
- The available signals strongly suggest it is abandoned: zero stars, zero dependents, and a last release date of 2016-06-10. There is no evident maintainer activity or security patching. For an upload handler, that lack of maintenance is a serious production concern.
- What is modera/file-uploader-bundle used for?
- It is intended to simplify and standardize uploading and storing files in Modera-based Symfony applications. It provides reusable upload handling for controllers and forms so files can be received, stored, and managed consistently across that ecosystem. It is not a general-purpose Laravel upload package.
- What Laravel alternatives should I use instead of modera/file-uploader-bundle?
- For simple uploads, use Laravel's native file upload and storage features. For media management, consider Spatie Media Library, and for resumable or chunked uploads evaluate Livewire/FilePond or tus-compatible Laravel packages. These options integrate with Laravel validation, storage, events, and the service container.
- Can I port modera/file-uploader-bundle to Laravel?
- A port would mean forking the bundle and rewriting its Symfony routing, dependency injection wiring, event hooks, and likely frontend assumptions into Laravel services and providers. At that point the original package provides little leverage. If you need a specific chunked-upload protocol, a small Laravel controller plus a modern frontend uploader is usually more practical.
- What security risks come with using modera/file-uploader-bundle in production?
- The main risks are unpatched vulnerabilities in an unmaintained upload handler, dependency conflicts from old Symfony components, and PHP version incompatibility. File uploads are a sensitive attack surface, so an abandoned handler is especially risky. A maintained Laravel package with active security support is the safer choice.
- Does modera/file-uploader-bundle support chunked or resumable uploads?
- The package description only states that it handles uploading and storing files consistently in Modera applications, and the FileUploader name suggests Modera-style frontend widgets. There is no documented Laravel support for chunked or resumable uploads. If resumability is required, evaluate tus-compatible Laravel packages or a custom controller and frontend uploader instead.
- How should I evaluate modera/file-uploader-bundle for a Laravel project?
- Treat any evaluation as a time-boxed spike only after confirming the exact feature gap. Try composer require in a throwaway Laravel app to expose dependency conflicts, and inspect its PHP/Symfony constraints and frontend assumptions. If conflicts are fatal or substantial rewriting is needed, use maintained Laravel alternatives rather than adopting this bundle.
Weaver
How can I help you explore Laravel packages today?