- Can I use locaine/lcn-image-uploader-bundle in a Laravel application?
- No. Despite being listed among PHP packages, locaine/lcn-image-uploader-bundle is a Symfony2 bundle that ships a Bundle class and Symfony service container configuration, not a Laravel service provider or facade. Laravel's architecture has no load-bearing equivalent for a Symfony bundle, so using it would require a hand-written bridge that becomes its own maintenance liability. For a feature this small, a Laravel-native implementation is the cheaper and safer path.
- How do I install lcn-image-uploader-bundle with Composer in a Laravel project?
- There is no supported way to install it in a Laravel project. The package has no Laravel package discovery, no service provider, and no facade, and pinning Symfony 2.x transitive dependencies such as symfony/http-foundation and symfony/dependency-injection alongside a modern Laravel install creates dependency conflicts with no clean resolution. Do not add it to composer.json for a Laravel application.
- Which PHP and Symfony versions does lcn-image-uploader-bundle support?
- It targets Symfony2, which reached end-of-life in November 2018, and almost certainly PHP 5.x through 7.0 using Symfony 2.x APIs that have been removed or renamed in Symfony 4, 5, 6, and 7. No Laravel version is supported by the package. Running it on a current PHP and Laravel stack would require an impractical compatibility effort.
- Is locaine/lcn-image-uploader-bundle maintained or safe for production?
- It shows no maintenance signal: 0 stars, 0 dependents, no fork activity, and no vulnerability reports, which means no community scrutiny of an upload code path. File uploads are among the highest-risk areas in any web application because of MIME and extension validation, path traversal, temp-file handling, storage permissions, and denial-of-service via oversized or malformed payloads. An unmaintained Symfony2-era uploader predates years of hardening guidance, so do not put it into production.
- What are the best Laravel alternatives for AJAX image uploads with preview and progress?
- Use Dropzone.js or FilePond on the client, or livewire/file-upload if your team is on Livewire, since all three provide previews, progress bars, and chunked uploads. On the server, a Laravel controller with a FormRequest using image|mimes:jpeg,png,webp|max:10240 and the Storage facade covers validation and disk-agnostic persistence. Add intervention/image for thumbnails and EXIF stripping, and push heavy processing onto a queued job.
- How should I validate uploaded images in Laravel instead of relying on this bundle?
- Create a FormRequest with rules such as image|mimes:jpeg,png,webp|max:10240, plus dimension rules if your UI requires specific sizes. Laravel's image rule inspects actual file content rather than trusting the client-supplied MIME type. Store files with generated filenames through the Storage facade and keep uploads out of paths that can execute PHP.
- How do I store uploads on S3 or a CDN in Laravel without this bundle?
- Laravel's Storage facade is disk-agnostic and supports local disk, S3, and GCS through config/filesystems.php. Use putFileAs or store with explicit visibility and serve files via temporary URLs or a CDN. This replaces the bundle's configurable-adapter concept with first-party Laravel abstractions that are already tested and maintained.
- Can I test an image upload feature in Laravel with PHPUnit or Pest?
- Yes. UploadedFile::fake()->image('photo.jpg') combined with Storage::fake('s3') gives fast, deterministic tests for validation rules, storage paths, and thumbnail generation. This is a strong argument for building Laravel-native, because the Symfony2 bundle offers no Laravel testing integration at all.
- How long does it take to replace this Symfony2 uploader with a Laravel-native implementation?
- Expect roughly 1 to 3 engineer-days for a production-quality uploader covering validation, storage abstraction, thumbnailing, and tests. That is almost certainly less effort than making the Symfony2 bundle run in a modern Laravel app, and the result is code your team owns. If your requirement is broader than a single uploader, spatie/laravel-medialibrary can reduce the build further.
- What should I do with legacy data if I migrate away from this bundle?
- Copy the stored files directly to your new disk and map the old records into a media or uploads table, using a polymorphic attachment if images belong to multiple models. Write a one-off Artisan command to import paths and metadata, regenerate thumbnails, and verify results. Then decommission the Symfony2 code rather than keeping it running as a compatibility layer.