- What Laravel versions does yellow-three/voyager support, and will it work with Laravel 10+?
- Voyager officially targets Laravel 8.x+, but based on the 2026 release date, it may not yet support Laravel 10+. Check the package’s changelog or GitHub issues for compatibility updates, as newer Laravel versions (e.g., 10+) introduce breaking changes like Livewire or Symfony components that could conflict with Voyager’s jQuery/Bootstrap stack.
- How does Voyager compare to Filament or Nova for admin panels in Laravel?
- Voyager is a lightweight, monolithic admin panel focused on quick CRUD scaffolding with Bootstrap/jQuery, while Filament and Nova are more modern, modular, and tightly integrated with Laravel’s ecosystem. Voyager lacks active maintenance and plugin documentation, making Filament or Nova better long-term choices for teams needing customization or API-first workflows.
- Can I use Voyager with Tailwind CSS or a modern frontend framework like React/Vue?
- Voyager is built with Bootstrap 4/5 and jQuery, so integrating Tailwind or SPAs requires custom theming or proxy routes. You’d need to override Blade templates or use Laravel Mix/Vite to compile assets separately. For React/Vue, consider Filament or building a custom admin panel with Inertia.js instead.
- What’s the installation process for Voyager, and do I need Node.js?
- Installation is straightforward: run `composer require yellow-three/voyager` and `php artisan voyager:install`. Node.js isn’t strictly required, but if you’re using Voyager’s default assets (Bootstrap/jQuery), you’ll need npm to compile frontend dependencies. The package publishes assets via `php artisan voyager:assets`, which can be customized.
- How does Voyager handle authentication? Can I integrate it with Sanctum or Passport?
- Voyager uses Laravel’s built-in auth (e.g., Breeze, Sanctum) but may conflict with existing admin guards. For Sanctum/Passport, you’ll need to manually configure middleware or override Voyager’s route protection. Test thoroughly, as Voyager’s default `/admin` routes might clash with API token-based auth flows.
- Is Voyager suitable for multi-tenancy or complex permission systems?
- Voyager’s permission system is basic and not designed for multi-tenancy out of the box. For complex RBAC, you’d need to extend the package’s `VoyagerPermission` model or integrate a third-party solution like Spatie’s Laravel-Permission. Consider alternatives like Filament or Nova if multi-tenancy is a core requirement.
- What are the performance implications of using Voyager in production?
- Voyager’s monolithic structure and Blade templates can bloat admin routes, especially with heavy media management (e.g., image uploads). Optimize by caching views, using CDN for assets, and ensuring your database is tuned for `voyager_*` tables. For high-traffic apps, consider lighter alternatives like Filament or a custom admin panel.
- How do I customize Voyager’s BREAD (Browse, Read, Edit, Add, Delete) functionality?
- Customizing BREAD operations requires overriding Voyager’s Blade templates or extending its Eloquent models. The package provides hooks like `voyager::bread`, but deep changes may need manual template/migration overrides. Document your changes carefully, as the package’s lack of active maintenance could make upgrades risky.
- Are there security risks with Voyager, given its unmaintained status?
- Voyager’s last release in 2026 and low star count suggest potential security risks, especially with dependencies like jQuery or Bootstrap. Audit the package’s `composer.json` for outdated libraries and consider forking or migrating to a maintained alternative (e.g., Filament) if security is critical. Always test CSRF, rate-limiting, and admin route protection.
- Can I use Voyager for a headless Laravel admin or API-only backend?
- Voyager is not designed for headless admin panels or API-first workflows. Its CRUD interfaces are Blade-based, and exposing REST endpoints requires manual API route wrapping. For headless setups, use Laravel’s built-in resources or a dedicated API package like Lighthouse or Filament’s API tools.