- Does mrgoodbytes8667/image-bundle work with Laravel?
- No. It is a Symfony bundle that depends on Symfony kernel bootstrapping: a Bundle subclass, a DependencyInjection extension, and a ConfigTreeBuilder, none of which Laravel's service-provider model invokes. There is no Illuminate\Support\ServiceProvider, no facade, no publishable config/image.php, and no Laravel auto-discovery entry. Composer requiring it into a Laravel app will not produce a working integration without an adapter you write and own.
- How do I install mrgoodbytes8667/image-bundle with Composer?
- In a Symfony application you would run composer require mrgoodbytes8667/image-bundle and register the bundle in config/bundles.php. In Laravel there is nothing to register because the package's DI wiring is never executed. Confirm the exact package name, version constraints, and required Symfony packages on Packagist before installing.
- What license is mrgoodbytes8667/image-bundle released under?
- Packagist reports NOASSERTION, so the actual license is unconfirmed. Read the LICENSE file in the GitHub repository and get legal sign-off before shipping it in a commercial product. An unresolved license is a hard blocker for most teams regardless of how good the code is.
- Which Symfony and PHP versions does this image bundle support?
- That is not documented in the available information, and there is no confirmed CI matrix. Symfony bundles usually pin symfony/framework-bundle to a specific major, so the supported range may already be behind current LTS lines. Read composer.json in the repository before planning any upgrade path.
- Can I use a Symfony image caching bundle inside a Laravel application?
- Only with custom integration work. One option is pulling the underlying caching service out of the bundle's DI glue and re-registering it manually in a Laravel service provider, which is feasible only if the image logic is cleanly separable from the bundle wiring. The other option is forking and rewriting the bootstrap layer. Either path makes your team the maintainer of a derivative work.
- Which image driver does mrgoodbytes8667/image-bundle use, GD, Imagick, or libvips?
- The driver is not stated in the overview, and it is also unclear whether processing is synchronous or queueable. Check the source for the driver abstraction and any memory or timeout configuration. Test large-image handling and concurrency before relying on it in production.
- Is this package production ready? How many stars and dependents does it have?
- It has 0 stars, 0 dependents, and a single release dated 2024-11-21. That means no field validation, no issue history to mine for known integration problems, and no evidence anyone has run it in production. With a single maintainer, any breaking change or abandonment is absorbed entirely by you.
- How does the image cache handle invalidation, cache keys, and CDN-friendly URLs?
- Unconfirmed. Ask whether it implements cache-key versioning so a changed source image invalidates its derivatives, plus stampede or lock protection under concurrent requests. CDN-friendly immutable URLs and a working invalidate path matter if you plan to front it with a CDN. If any of these are missing, budget to build them yourself.
- Are there security risks with user-supplied image paths or remote source URLs?
- Potentially, and it needs review. Ask specifically how it handles user-supplied paths and remote source URLs, covering path traversal, SSRF, and decompression-bomb limits. No security advisories are listed, but with one release and no downstream consumers there has been very little external scrutiny.
- What are the alternatives to mrgoodbytes8667/image-bundle for image resizing and caching?
- On Laravel, intervention/image combined with Laravel's cache is the mature choice; on the Symfony side it is liip/imagine-bundle. A managed CDN or image service removes the whole problem class. A safer pattern is defining an internal ImageCacheContract with url(), path(), and invalidate(), then implementing it with a supported library rather than depending on this bundle directly.