Weave Code
Pel Bundle Laravel Package
kitano/pel-bundle
A Symfony bundle that integrates the PHP Exif Library (PEL), giving your application a service-based way to read, edit, and write EXIF metadata in JPEG and TIFF images through familiar dependency injection and configuration.
PEL Symfony integration bundle
Frequently asked questions about Pel Bundle
- Is kitano/pel-bundle a Laravel package?
- No. It is a Symfony bundle that relies on Symfony's kernel, bundle registration, DI extension, and compiler-pass lifecycle, none of which Laravel's service container honors. You cannot drop it into a Laravel app and expect it to boot or register services automatically.
- Can I install kitano/pel-bundle with Composer in a Laravel project?
- Composer will install the code, but installation is not integration. Laravel will not auto-discover or boot the bundle, and the kitano_pel configuration tree will not be loaded. You would need a custom service provider to replicate the bundle's wiring.
- What does kitano/pel-bundle actually add over the PEL library?
- The bundle's contribution is Symfony container wiring and a configuration convention for the PHP Exif Library. It registers PEL services and normalizes kitano_pel config, while the actual EXIF reading, editing, and writing is done by the underlying library. In Laravel you are better off depending on PEL directly or using a maintained EXIF package.
- How do I port kitano/pel-bundle to a Laravel service provider?
- You would copy the bundle's service definitions, config normalization, and any factory logic into a Laravel service provider, then bind the PEL service as a singleton. That is a few hundred lines of glue for a framework you are not using. The TPM assessment calls this feasible but pointless because the glue is the only thing the bundle adds.
- Does kitano/pel-bundle support Laravel 9, 10, or 11?
- No. The bundle targets Symfony's bundle system and dates from the PHP 5.x era; it has no declared support for Laravel 9/10/11 or PHP 8.1+. Running it on a modern Laravel stack would require compatibility work with no upstream maintenance.
- Is kitano/pel-bundle maintained and safe for production?
- The repository shows 4 stars, 0 dependents, and a composite score of 0.02, which is a strong abandonment signal. Expect PHP 5.x-era constraints, no PHP 8 support, no security response, and a dead issue tracker. For production, treat it as unmaintained and avoid depending on it.
- What are alternatives to kitano/pel-bundle for EXIF editing in Laravel?
- Depend on the underlying PEL library directly if you need its exact API, or use a maintained Laravel-friendly package that wraps PHP's exif extension or Intervention Image. Skipping the Symfony bundle glue is the key decision; the bundle itself adds no EXIF functionality.
- How do I configure kitano_pel in Laravel?
- There is no kitano_pel configuration tree in Laravel because that is a Symfony DI extension feature. In Laravel you would create config/pel.php, publish it, and bind a configured PEL service in a provider. That is custom glue, not something the bundle provides.
- Can I test kitano/pel-bundle inside a Laravel test suite?
- Not directly. The bundle expects a Symfony kernel and container, and Laravel's testing helpers do not boot bundles. You would have to isolate the PEL library and test your own wrapper, or stand up a Symfony kernel just for tests, which adds complexity for little benefit.
- When should I use kitano/pel-bundle versus writing my own integration?
- Use it only if you are maintaining a Symfony application that already uses Kitano bundles and needs the kitano_pel service convention. For a Laravel app, writing a small PEL wrapper or using a maintained EXIF package is faster, safer, and avoids an abandoned dependency.
Weaver
How can I help you explore Laravel packages today?