Weave Code
Image Bundle Laravel Package
small-team/image-bundle
small-team/image-bundle is a lightweight PHP package that brings simple image handling to Laravel applications. It offers framework-friendly helpers for processing and serving images with minimal configuration and a small footprint.
Image manipulation bundle for Symfony 2
Frequently asked questions about Image Bundle
- Can I use small-team/image-bundle in a Laravel application?
- No, not in any practical sense. It is a Symfony 2 bundle, which is a Symfony-specific packaging primitive built around a DependencyInjection extension, a Configuration tree, service definitions, and Symfony resource conventions. Laravel has no equivalent for any of that: there is no service provider, no facade, no publishable config, and no view namespace, so the bundle's wiring never resolves in Laravel's container. The only realistic option is stripping the bundle packaging off and reaching the raw image code underneath, at which point you are vendoring fragments rather than using the package.
- Is small-team/image-bundle still maintained?
- No. The last release was December 2018, it has a single maintainer, zero dependents, and one star on the repository. That makes it effectively a personal artifact rather than a maintained library. There is no security response process, no CVE path, and no upgrade path to current PHP versions.
- Does small-team/image-bundle support PHP 8.1+ and current Laravel versions?
- Almost certainly not. Symfony 2 reached end of life in 2019, and the bundle's Composer constraint will target PHP 5.x or early 7.x, which is incompatible with the PHP 8.1+ floor of any currently supported Laravel release. Even if Composer's platform checks were bypassed, the runtime code targets an API surface that no longer exists. There is no maintained upgrade path.
- How do I install small-team/image-bundle with Composer?
- You can run composer require, but installing it does not get you a working integration in Laravel. The bundle expects Symfony's kernel and container to boot its extension and load services, neither of which exists in a Laravel app. You would also pull its own abandoned transitive dependencies, including Symfony 2 components and image drivers, into your lockfile.
- What should I use instead of small-team/image-bundle in Laravel?
- Use a maintained, framework-native library. intervention/image is the closest functional analogue and ships with a Laravel service provider and facade plus GD or Imagick drivers. spatie/image and spatie/laravel-image-optimizer cover fluent transformations plus post-processing optimisation, and league/glide fits dynamic, URL-parameterised resizing behind a cache or CDN.
- Can I extract the image manipulation code and drop the Symfony bundle packaging?
- Possibly, but only if the driver delegation layer is cleanly separable from the Symfony glue, and the project provides no documented public API or tests to confirm that. If the non-bundle classes can be lifted, you would expose them behind a single ImageTransformer interface so the driver stays swappable. Treat the bundle as a reference implementation or spec rather than a dependency, and budget for owning the fork.
- Does it work with Laravel Storage, UploadedFile, or S3 disks?
- No. Its file handling assumes Symfony's Filesystem and HttpFoundation components, so Laravel's Storage disks, UploadedFile objects, and S3 drivers would need an adapter layer at every boundary. That adapter work is non-trivial and would sit on top of code that is no longer receiving fixes.
- Is small-team/image-bundle safe to run in production?
- It carries high, concentrated risk. The project is abandoned, has no security disclosure process or CVE path, and installing it drags abandoned transitive dependencies into your lockfile. With negligible adoption there are no community field reports for edge cases such as corrupt uploads, EXIF rotation, CMYK inputs, EXIF-based decompression bombs, or animated GIF handling.
- How do I migrate a legacy Symfony 2 app that uses this bundle over to Laravel?
- Start by inventorying every transformation the bundle performs in production, such as resize, crop, watermark, format conversion, quality, and filters, and capture sample inputs and outputs as golden files. Confirm no business logic lives inside the bundle beyond the transformation call, then port each transformation as a small tested class over Intervention Image or Glide behind a single ImageTransformer interface. Finish with parity tests against the golden files before cutting over.
- What license is small-team/image-bundle released under, and can I fork it?
- It is MIT licensed, which is the one clean signal in the package and permits forking and code extraction. If you do extract code, assign clear ownership of the fork and a budget to keep it patched against PHP upgrades. In most cases re-implementing the transformations on a maintained library is cheaper than maintaining an extracted fork.
Weaver
How can I help you explore Laravel packages today?