Weave Code
Image Bundle Laravel Package
integrated/image-bundle
Integrated Image Bundle for Symfony provides image management with image type configuration, filtering, cropping and resizing via LiipImagineBundle, plus a Symfony form type and Twig helpers for upload and display.
At a glance
Frequently asked questions about Image Bundle
- Does integrated/image-bundle work with Laravel?
- Probably not without significant work. It is built as a Symfony bundle, wired through Bundle classes, DI extensions and YAML or XML service definitions, while Laravel expects service providers, facades and publishable config. Nothing in the public material shows a Laravel service provider or an extra.laravel.providers auto-discovery block, so treat Laravel support as unproven until you read the source.
- How do I install integrated/image-bundle?
- Installation is via Composer, but the package has zero stars, zero dependents and no evidence of a tagged release, so a floating constraint is risky. Pin to a specific commit SHA if you experiment with it, and check composer.json for PHP and framework constraints first. There is also no published documentation describing post-install configuration or bundle registration.
- Which Laravel and PHP versions does integrated/image-bundle support?
- Unverifiable from public signals. The description points to a Symfony bundle built on LiipImagineBundle, so the relevant constraints are likely symfony/* rather than illuminate/*, and no Laravel version range is stated anywhere. Read composer.json rather than assuming compatibility with your PHP or Laravel release.
- What does integrated/image-bundle offer that Intervention Image or Spatie Media Library does not?
- Nothing in the available material answers that. The described scope, from upload validation through resizing, cropping, format conversion, derivative caching and responsive variants, overlaps heavily with Intervention Image, Glide, Spatie Media Library and LiipImagineBundle itself. It looks like a thin configuration layer over LiipImagineBundle, so adopting it may just add a stale wrapper around a dependency you could pin directly.
- Does integrated/image-bundle support S3 or Laravel filesystem disks?
- Unknown, and this is a dealbreaker for most Laravel deployments. The package advertises pluggable storage and cache adapters, but there is no confirmation that it operates on Laravel filesystem disks or S3-compatible storage rather than hardcoded local paths. Confirm this from source before scoping any work, because an integration that cannot move to S3 is dead on arrival.
- Is integrated/image-bundle safe to use in production?
- Risk is high. It has zero stars, zero dependents, no visible installed base and no obvious security disclosure channel, so there is no upstream patch stream for CVEs, PHP deprecations or framework major-version drift. If you adopt it, pin to a commit SHA, vendor it, and hide it behind an internal interface so it stays a swappable detail.
- What imaging engine does integrated/image-bundle use?
- It delegates filtering, cropping and resizing to LiipImagineBundle, which runs on GD or Imagick through the Imagine library depending on your configuration. The README does not document transform semantics such as resize modes, quality defaults, EXIF stripping or cache-key derivation. That means engineer-days reading source before you know what the package actually does.
- Can I use integrated/image-bundle for thumbnails and responsive images?
- In a Symfony application, yes, since it advertises automatic thumbnail and responsive variant generation through LiipImagineBundle filters. In Laravel you would have to rebuild that pipeline, for example with Intervention Image plus a queued job. The Twig helpers and Symfony form type it ships do not carry over.
- What are the best alternatives to integrated/image-bundle for Laravel?
- For Laravel, Intervention Image covers transforms, Spatie Media Library covers uploads, disk-backed storage and conversions, and Glide provides on-the-fly transformation URLs. These are maintained, widely deployed and documented, which is what you want for a commodity media pipeline. None of them require a Symfony bundle bridge or an unknown vendor dependency.
- How should I evaluate integrated/image-bundle before adding it to a Laravel project?
- Run a one-day spike behind an internal ImageProcessor contract covering resize, crop, convert and optimize, with Intervention Image as the fallback implementation. During the spike confirm whether it ships a Laravel service provider, whether any tagged release exists, the license, the maintainer identity and the underlying imaging engine. If the spike does not prove differentiated capability, skip it: the opportunity score of 16.63 is a signal to look, not a signal to adopt.
Weaver
How can I help you explore Laravel packages today?