- Does onadrog/imageconverterbundle work with Laravel 10 or 11?
- The package is published as a Symfony bundle, and its naming and release vocabulary come from the Symfony/EasyAdmin world rather than Laravel. No Laravel service provider, facade, config file, or version constraint for Laravel 10 or 11 is documented in the material available. Treat any Laravel support as unverified until you confirm it against the actual source, and do not assume it will register automatically in a Laravel app.
- How do I install onadrog/imageconverterbundle with Composer?
- Installation is via Composer against the onadrog/imageconverterbundle package name. In Symfony you then register the bundle in config/bundles.php and configure it through the bundle's configuration. There is no documented Laravel installation path, so a Laravel host would need a manual wrapper or an explicit service provider before the FormType or conversion service is usable.
- What changed in v1.1.0 and are there breaking changes?
- The v1.1.0 notes describe two additions: client-side JavaScript image conversion and a modal-driven relational entity picker that lets editors choose an existing image or upload a new one. No breaking changes are stated, but the modal may alter existing form or widget markup and route expectations, and unversioned asset changes can break already-published views. Upgrade in a sandbox with a copy of production media before rolling out, and diff any published templates.
- Does this package convert images on the client or on the server?
- v1.1.0 introduces a JavaScript conversion path, but the release notes do not state whether it is opt-in, the default, or a fallback alongside the existing PHP-side handling. That ambiguity is a rollout risk, because a silent switch from server-side conversion to browser-side conversion changes both quality and security guarantees. Confirm the default behavior in the source before enabling it in production.
- Is client-side JavaScript image conversion safe for user uploads?
- No. Anything converted in the browser is untrusted input by definition and can be bypassed by disabling JavaScript or crafting a direct request, so server-side validation, MIME sniffing, and re-encoding must remain authoritative. If v1.1.0 replaces the server-side conversion path rather than supplementing it, that is a security regression. Keep a server-side re-encode step regardless of what the client produces.
- Which image formats does the JavaScript converter support, and what is the fallback?
- Canvas- and WebCodecs-based conversion has known gaps, including HEIC input, CMYK JPEGs, animated GIF and WebP, ICC profiles, and EXIF orientation handling. Silent quality loss or metadata stripping is likely and hard to catch in QA, because the output still looks valid. The notes do not document maximum dimensions, file sizes, or the fallback for unsupported formats, so define your own server-side limits and fallback path.
- Can I use the modal image picker with Livewire, Filament or Nova?
- The modal picker is a presentation-layer feature, which makes it a reasonable conceptual fit for Livewire, Alpine, Filament, or Nova admin surfaces. However, it likely assumes specific DOM and JavaScript contracts, so integration is higher risk in apps with custom form markup. Test it against your exact front-end stack before committing, and check whether it ships its own views and routes.
- Which relationship types does the image picker support, and does it respect authorization?
- The relational picker implies a belongs-to or morph-to style image model, which maps cleanly onto Eloquent conventions. Support for many-to-many or pivot relationships, and whether existing policies and gates are enforced when browsing media, is not documented. Verify authorization behavior explicitly if editors should only see images they are permitted to access.
- Do I need to publish JS and CSS assets, and does it work with Vite?
- Adding a JavaScript conversion path means the package now has a front-end asset pipeline dependency on top of PHP image handling. Plan for publishing JS and CSS, coexistence with Vite or Mix, and a Content Security Policy that permits the bundle's scripts. A strict CSP that blocks inline or third-party scripts will break the modal and converter outright.
- What are the alternatives for WebP conversion in a Laravel application?
- For server-side conversion, intervention/image, spatie/image, and Glide over Flysystem are the common Laravel-friendly options, all of which keep processing on the server. If you want the relational media picker pattern, spatie/laravel-medialibrary plus an admin panel component covers similar ground. Given the framework mismatch here, evaluating one of those is often faster than wrapping a Symfony bundle.