- What is joy/voyager-core used for in a Laravel Voyager admin panel?
- joy/voyager-core is a shared foundation package for the joy-voyager-* family of Laravel admin panel tools. It puts common configuration, helpers, service providers, and building blocks in one place so sibling packages can reuse them. It is not a standalone admin panel feature; it is glue for Voyager-style admin interfaces.
- How do I install joy/voyager-core with Composer?
- You install it like most Laravel packages by running composer require joy/voyager-core in a Laravel application that already uses Voyager. Because it is a core package for the joy-voyager suite, confirm whether one of the sibling joy-voyager packages requires it before adding it directly. Pin a tagged release rather than dev-main and commit your composer.lock.
- How do I publish and configure joy/voyager-core settings?
- The package follows standard Laravel provider and configuration conventions, so any publishable config or assets should be exposed through php artisan vendor:publish. After publishing, review the generated config file and align it with your Voyager setup. If no publish tag is documented, inspect the service provider to see exactly which config keys and files it registers.
- Which Laravel and PHP versions does joy/voyager-core support?
- The exact Laravel, PHP, and Voyager version matrix is not established in the package overview, so check the composer.json constraints before committing. Voyager itself is mature and slow-moving, which makes version alignment the main integration risk. Validate against one current Laravel LTS and your production PHP version in an isolated environment.
- Is joy/voyager-core required by other joy-voyager packages?
- As a core package for the joy-voyager-* family, it is likely a shared dependency for sibling modules rather than optional glue. That means adopting it may also pull in other low-adoption joy-voyager packages and expand your review surface. Confirm whether any joy-voyager package you actually need lists it as a hard requirement.
- Does joy/voyager-core override Voyager vendor files or modify core behavior?
- The package description says it adds VoyagerCore support to Voyager, but it does not confirm whether that means benign service provider registration or invasive vendor patching. Read the service provider and check for class overrides, monkey-patching, or changes inside Voyager's vendor tree before adopting it. This distinction is critical because deep hooks make Laravel and Voyager upgrades fragile.
- Is joy/voyager-core production-ready and actively maintained?
- Treat it as high-risk until audited: it has a single maintainer, very few stars, zero dependents, and effectively no external validation. There is a 2024 release, but low adoption means defects are unlikely to be surfaced by a community. For production, perform a code audit and consider an internal fork rather than relying on upstream responsiveness.
- How should I test joy/voyager-core before adopting it in production?
- Start with an isolated spike branch, install the package, and verify that Voyager's admin boots and its services register correctly. Add a boot smoke test covering admin login, dashboard render, one CRUD screen, and config publishing. Then run a small compatibility matrix with one current Laravel LTS and one prior version on your production PHP version.
- Can I fork joy/voyager-core or vendor it privately?
- Yes, the MIT license and standard Composer packaging make it a reasonable adopt-and-fork candidate. Mirror the code into an internal VCS repository or private Packagist so you control patches, pinning, and security review. Avoid depending on dev-main upstream and keep a committed composer.lock for reproducible builds.
- What are alternatives to joy/voyager-core for Laravel admin panels?
- If you are not already committed to Voyager, evaluate alternatives such as using Voyager directly, Filament, Laravel Nova, or Backpack before adding a low-adoption core package. joy/voyager-core only has architectural relevance inside the Voyager and joy-voyager ecosystem. If you do use Voyager, check whether its own extension points cover your needs without this shared package.