Weave Code
Imagekit Bundle Laravel Package
geekcell/imagekit-bundle
GeekCell ImageKit Bundle provides Symfony integration for ImageKit.io, with dependency-injection configuration and helpers for uploading, transforming, and delivering optimized images via ImageKit’s CDN. It simplifies service setup for media workflows in PHP applications.
A Symfony bundle for ImageKit integration.
Frequently asked questions about Imagekit Bundle
- Is geekcell/imagekit-bundle compatible with Laravel?
- No, not natively. It is a Symfony bundle that depends on Symfony bundle registration, a DI extension, and services.yaml loading, none of which Laravel auto-discovers. You would have to manually port its service definitions into a Laravel service provider. For Laravel, use the official imagekit/imagekit PHP SDK instead.
- How do I install geekcell/imagekit-bundle in a Laravel app?
- You generally should not. Composer may install it, but Laravel will not register the bundle or load its Symfony DI configuration. Making it work means rewriting the wiring yourself, at which point you have effectively written your own integration. Install imagekit/imagekit and bind it in a service provider.
- What Laravel versions does geekcell/imagekit-bundle support?
- None officially. The package targets Symfony, and its last release was July 2023, so its Symfony component and PHP constraints likely conflict with Laravel 11 or 12, which use Symfony 7 components. Check composer.json constraints before attempting anything.
- Does geekcell/imagekit-bundle work with Laravel 11 or 12?
- Very likely not without changes. A 2023 Symfony bundle will typically pin Symfony 5.4 or 6.x components and an older ImageKit SDK major, which can conflict with the Symfony 7 components Laravel 11 and 12 depend on. Even if Composer resolves, the bundle's DI layer still will not run in Laravel.
- What is the best Laravel alternative to geekcell/imagekit-bundle?
- Use ImageKit's official PHP SDK, imagekit/imagekit. Create config/imagekit.php with your public key, private key, and URL endpoint, bind an ImageKit\ImageKit singleton in a service provider, and optionally add a facade. That reproduces the bundle's useful surface area in under an hour.
- Does geekcell/imagekit-bundle handle image uploads or only URL generation?
- It is a thin Symfony wrapper over the ImageKit SDK, so its capability depends on the SDK version it pins. The overview emphasizes URL generation and transformations, and the bundle itself adds mostly configuration and DI wiring. For uploads, signed URLs, and retries, verify against the official SDK rather than assuming the bundle covers them.
- Is geekcell/imagekit-bundle maintained and safe for production?
- No. It appears archived, with no releases since July 2023, zero stars, and no dependents, so there are no bug fixes, security patches, or compatibility updates. That is a significant risk for production. If you must reuse any code, fork it under MIT and own the maintenance.
- How do I configure ImageKit in Laravel without this bundle?
- Add imagekit/imagekit via Composer, create config/imagekit.php with public_key, private_key, and url_endpoint values sourced from env, and register a singleton binding for ImageKit\ImageKit in a service provider. You can then inject the client anywhere or expose a facade. This avoids Symfony bundle wiring entirely.
- Can I use geekcell/imagekit-bundle in a hybrid Symfony and Laravel project?
- Only within the Symfony side. Laravel's container will not execute the bundle's extension or compiler passes, so the Laravel side still needs its own binding. If you have existing Symfony services, consider vendoring the bundle code under app/Support and stripping the DI layer. Do not rely on cross-framework auto-wiring.
- How should I test an ImageKit integration in Laravel?
- Keep the ImageKit client behind an interface or a thin URL builder so you can fake it in tests. Unit-test URL construction and transformation parameters without network calls, and use HTTP fakes for upload paths. The bundle's PSR-friendly core is not a reason to adopt it, since the official SDK is testable the same way.
Weaver
How can I help you explore Laravel packages today?