- Does OrcaHarpoon require a browser extension, and which browsers does it support?
- Yes, OrcaHarpoon likely relies on a browser extension for visual inspection, though this isn’t explicitly stated in the README. Based on similar tools, it probably supports Chrome and Firefox, but verify with the maintainers for exact compatibility. Headless environments or CI/CD pipelines won’t support the visual workflow.
- How do I customize the AI refactor prompts for my project’s Livewire naming conventions?
- The package generates AI prompts for refactoring, but customization isn’t detailed in the README. You may need to manually edit the session-stored prompt or extend the middleware to inject project-specific patterns (e.g., custom property naming). Check if the `harpoon-complete` event allows post-generation modifications.
- Will OrcaHarpoon add noticeable performance overhead during development?
- The middleware auto-injects only in local environments, so overhead should be minimal. Visual inspection features like live highlighting may introduce slight latency, but the tool is designed for development use. Test in your environment to confirm, especially if working with complex pages.
- Can I use OrcaHarpoon in shared hosting or multi-tenant environments with restricted middleware?
- OrcaHarpoon’s middleware is local-only, so it won’t interfere with production or shared hosting. However, the visual inspection feature requires a browser extension and won’t work in headless or restricted environments. For shared hosting, focus on the generated components and manually replace `@livewire` tags in production.
- How do I unit or feature test components generated by OrcaHarpoon?
- Generated components follow standard Livewire conventions, so you can test them like any other Livewire class using Laravel’s testing tools. The Blade views and PHP classes are scaffolded with best practices, but validate edge cases (e.g., dynamic classes, nested forms) manually or with custom test suites. No built-in testing hooks are mentioned, so rely on Laravel’s Livewire testing utilities.
- Is OrcaHarpoon compatible with Laravel 11 or Livewire 3, or only Laravel 12 + Livewire 4?
- OrcaHarpoon has a **hard dependency on Laravel 12 and Livewire 4**, as stated in the badges and requirements. Components generated may not work with older versions. If you’re on Laravel 11 or Livewire 3, consider manual component generation or alternative tools like Livewire’s CLI until you upgrade.
- What happens if I click an element with complex nested structures or dynamic classes?
- OrcaHarpoon captures the entire element and its children, but complex nested structures (e.g., deeply nested forms, dynamic classes) may require manual review. The AI refactor prompt aims to handle replacements, but edge cases might need adjustments. Test with critical components first to validate generated output.
- Can I integrate OrcaHarpoon into my CI/CD pipeline to auto-generate components?
- No, OrcaHarpoon is designed for **local development only** and relies on browser-based inspection. While it generates components automatically, the visual workflow and AI refactoring won’t work in CI/CD. Use it during development, then manually merge generated files into your pipeline or version control.
- Are there alternatives to OrcaHarpoon for Livewire component generation?
- For Livewire, alternatives include **Livewire’s official CLI** (`livewire:make component`) for manual scaffolding, or **Laravel Breeze/Jetstream** for pre-built components. Tools like **Laravel Shift** or **Refactoring.Guru** offer broader refactoring but lack Livewire-specific visual inspection. OrcaHarpoon’s strength is its **one-click visual workflow** with AI-assisted refactoring.
- How do I handle generated components in a modular Laravel setup (e.g., with Spatie Laravel Modules)?
- OrcaHarpoon automatically places components in `Modules/{Module}/app/Livewire/` and registers them via the module’s service provider. If you’re using Spatie’s modules, ensure your module structure aligns with the generated paths. The tool includes module metadata out of the box, so no additional configuration is needed for basic modular setups.