- What is lacv/pipo-scanner used for in Laravel?
- lacv/pipo-scanner is a Filament v3/v5 document scanner component for Laravel. It provides camera capture, edge detection, crop, filters, and multi-page PDF output. It is a thin integration layer for Pipo Scanner rather than a pure PHP document-processing library.
- Does lacv/pipo-scanner support Filament v3 and v5?
- The package description targets Filament v3 and v5. The provided material does not include a tested compatibility matrix, so confirm your exact Filament and Livewire versions before starting a spike. Filament minor upgrades should be treated as part of your normal dependency review.
- How do I install lacv/pipo-scanner in a Laravel app?
- Install it as a Composer dependency using the package name lacv/pipo-scanner, then follow the documented step-by-step integration example and configuration reference. The v1.0.2 release is documentation and licensing only, so it does not change the integration steps from v1.0.1. Check the README for the required Filament and Livewire setup in your application.
- Which Laravel and Livewire versions does lacv/pipo-scanner support?
- Livewire compatibility is central because the package exposes a browser event and a server-side Livewire method. The provided release material does not state a tested Laravel or Livewire version matrix. Confirm support for your Livewire major version, especially if you are on Livewire v3, before adoption.
- How does camera capture work in the Pipo Scanner Filament component?
- The component uses the browser and device camera surface for capture, with client-side handling of device concerns and server-side state reconciliation through Livewire. It dispatches a browser event in addition to exposing a Livewire method. This dual-path design is useful, but it means camera behavior depends on the browser and device rather than PHP alone.
- Can lacv/pipo-scanner create multi-page PDFs from scans?
- Yes, the package is described as supporting multi-page PDF output alongside crop, filters, and edge detection. The exact PDF engine and configuration options are not detailed in the provided material. Verify output quality, file size, and storage handling in a proof of concept.
- What happens if camera permission is denied or the browser is unsupported?
- The provided material does not document permission-denial or unsupported-browser behavior. Device and browser-dependent packages often fail in ways that do not reproduce in CI, such as permission prompts, insecure-context restrictions, or OS-level camera gating. Test denial, unsupported browsers, and non-HTTPS origins explicitly before relying on it.
- Does lacv/pipo-scanner work on mobile devices and non-HTTPS origins?
- The release notes reference Android, iOS, and HTTP, which implies browser and device-dependent behavior. Non-HTTPS origins can affect camera access in browsers, but the package material does not state its exact support policy. Validate on your target mobile devices and secure-context requirements.
- Is lacv/pipo-scanner production-ready and does it have tests?
- Test coverage is not stated in the provided material, and the package is at a young 1.0.x stage with documentation still being filled in at patch level. The v1.0.2 release itself is low risk because it is docs and licensing only, but the underlying package still carries browser and Livewire upgrade risk. Wrap its public surface in a thin adapter so you can replace it with bounded effort.
- Is lacv/pipo-scanner MIT licensed and what is the fallback if it is abandoned?
- Yes, the package added an explicit MIT LICENSE file, which resolves the licensing question. If it is abandoned, the recommended fallback is the thin internal adapter around its browser event and Livewire method, so only one place in your codebase needs replacement. That wrapper is the main exit cost.