Weave Code
File Uploader Bundle Laravel Package
intaro/file-uploader-bundle
A Symfony bundle for adding file upload functionality to PHP applications. It provides upload handling, configuration, and integration points for managing uploaded files within Symfony projects, helping developers implement file uploads with less custom boilerplate.
Simplifies file uploading in Symfony2
Frequently asked questions about File Uploader Bundle
- Is intaro/file-uploader-bundle a Laravel package?
- No. It is a Symfony2 bundle that ships a Bundle class, service-container wiring, event-dispatcher subscribers, and a configuration tree, with no Laravel service provider, facade, or illuminate/* dependency. Laravel's package auto-discovery will not register it, and installing it in a Laravel app would be at best inert. Treat it as a reference design, not a runtime dependency.
- Can I install intaro/file-uploader-bundle in a Laravel application?
- You can try, but Composer will usually stop you: Symfony2-era bundles commonly constrain php to >=5.3 with symfony/* ~2.x, which conflicts with the modern Symfony majors Laravel pins. Even if resolution succeeded, there is no Laravel integration layer to boot the bundle. The practical path is to reimplement the concepts against Laravel Storage and UploadedFile.
- What Laravel version does intaro/file-uploader-bundle support?
- None officially. The package targets Symfony2, which reached end of life in 2018, and it has no Laravel version constraints, service provider, or auto-discovery entry. There is no supported Laravel version to point at. Use Laravel's native upload stack instead.
- Why does Composer fail when installing this Symfony bundle with Laravel?
- Laravel pins modern symfony/http-foundation, symfony/event-dispatcher, and symfony/console, while Symfony2-era bundles constrain symfony/* to ~2.x and often php to >=5.3. Those constraints are mutually exclusive, so resolution fails or forces an unacceptable downgrade. Do not downgrade Symfony components to satisfy a 3-star dependency.
- What are good alternatives to intaro/file-uploader-bundle for Laravel?
- Laravel already provides the equivalent primitives: UploadedFile::storeAs for atomic writes, the Storage facade over Flysystem for local or S3 disks, and file, mimes, and max validation rules. For Livewire apps, WithFileUploads covers progress and temporary uploads. For a drop-in UI, consider Uppy, FilePond, or Dropzone paired with a Laravel upload endpoint.
- How do I implement chunked file uploads in Laravel without this bundle?
- Use Illuminate\Http\UploadedFile with a chunked client such as Resumable.js or Uppy, write each chunk to a temporary Storage path, then assemble and move the final file with storeAs. Add validation rules like file, mimes, and max on a FormRequest. A queued job can handle assembly and image derivatives so the request stays fast.
- How do I handle AJAX multiple file uploads with progress in Laravel?
- Accept multipart requests on a route, validate each file with a FormRequest, and store via UploadedFile::storeAs on the disk you need. Return JSON with the stored path or a temporary key, and let the front end use XMLHttpRequest upload progress events or a library like FilePond. For large files, chunk client-side and reassemble server-side.
- How do I clean up orphaned uploaded files in Laravel?
- Store uploads under a temporary prefix, persist the reference on the model when the form saves, and run a scheduled Artisan command that lists unreferenced keys and deletes them. This reuses the bundle's best idea, decoupling the upload endpoint from the entity write, without its Symfony dependencies. Wrap the logic behind a FileStorageService interface so the storage decision stays swappable.
- Is intaro/file-uploader-bundle maintained and safe for production?
- Signals are weak: roughly 3 stars, 0 dependents, a composite score near 0.405, and a Symfony2 target that has been EOL since 2018. The 2024-10-11 release tag looks more like a maintenance tag than active feature work. Because upload code handles untrusted input, the lack of peer review and a security response process is a real risk.
- How do I write tests for AJAX file uploads in Laravel?
- Use UploadedFile::fake() with Storage::fake() in a feature test, post to your upload route, and assert the file exists on the fake disk. For chunked uploads, post each chunk and assert the assembled file is present. This is straightforward with Laravel's native stack and is another reason not to bolt on a Symfony2 bundle.
Weaver
How can I help you explore Laravel packages today?