- Is insitaction/easycrop a Laravel package?
- No. It is published as EasyCropBundle, a Symfony bundle registered through Symfony's DI container, routing, and configuration. The image-cropping workflow and Stimulus-based UI are reusable, but the PHP integration layer is Symfony-specific rather than Laravel-native.
- Can I install insitaction/easycrop with Composer in a Laravel app?
- Usually not as a drop-in dependency. Because it is a Symfony bundle, Composer will resolve Symfony framework packages alongside your Laravel app, and Laravel 10's Symfony 6.x components are likely to conflict with the bundle's Symfony 7 support. For Laravel, treat it as a reference implementation or extract only the Stimulus UI.
- Which Laravel versions does EasyCrop support?
- There is no official Laravel support statement. Version 1.0.5 adds Symfony 7 support, which aligns with Laravel 11 and 12 because they ship Symfony 7 components. Laravel 10 uses Symfony 6.x and will likely fail Composer resolution without constraint changes.
- What PHP and Symfony versions does EasyCrop require?
- The v1.0.5 release explicitly allows Symfony 7, which implies a PHP 8.2+ baseline for the bundle. The exact minimum PHP version and whether PHP 8.1 remains supported should be confirmed in the package's composer.json before you plan an integration.
- Does EasyCrop handle image formats with Intervention Image?
- The package description says it works with common image formats via Intervention Image, so image decoding and output are handled by that library. The v1.0.5 release also fixed a dependency bug involving Stimulus and MIME type handling. You should still verify where server-side MIME validation lives and whether the fix addressed a correctness bug or a security bypass.
- Is EasyCrop actively maintained?
- It has a single known maintainer, negligible adoption (1 star and 0 dependents), and no Laravel ecosystem presence. A release landed after the December 2023 baseline and documentation was updated, so it is not abandoned. However, there is no published support policy, backward-compatibility policy, or release cadence commitment.
- Can I reuse EasyCrop's Stimulus controller in Laravel with Vite?
- Yes, that is the most credible reuse path. Stimulus is framework-agnostic and runs fine under Laravel when installed via @hotwired/stimulus and Vite, so you can lift the controller, markup, and CSS into a Blade partial with a Vite entrypoint. First confirm the controllers are published as standalone assets rather than injected through Symfony UX or Twig helpers.
- What should I use instead of EasyCrop for Laravel image cropping?
- For a Laravel-native solution, combine a JavaScript cropper UI with Laravel controllers, form requests, storage disks, and Intervention Image or Glide for server-side processing. You can still borrow EasyCrop's Stimulus controller and crop-workflow ideas. A custom Laravel implementation avoids Symfony DI, routing, and bundle constraints.
- Is EasyCrop production-ready and secure?
- The technical risk is high: low adoption, a single maintainer, and no security or support policy. The package does perform server-side MIME validation, but v1.0.5 fixed a MIME-type dependency defect, and it is unclear whether that was a correctness bug or a security bypass. Before production use, audit upload validation, EXIF orientation handling, size limits, and path traversal protections.
- How do I migrate EasyCrop from Symfony to Laravel?
- Run a time-boxed spike: inspect composer.json for the exact Symfony 7 constraint set and PHP floor, then attempt a dry-run install against your target Laravel version. If Composer conflicts, lift the Stimulus controller and associated CSS/markup into Blade with Vite, and reimplement the server endpoint using Laravel controllers, form requests, storage disks, and Intervention Image. Treat the Symfony bundle config, DI extension, validation, and controller as a reference implementation.