- What is monstrex/voyager-extension and what does it do?
- It is an extension package for Laravel Voyager that adds extra tools and helpers to the admin panel for building and managing custom BREAD interfaces, forms, and backend features. It is a bounded add-on rather than a framework fork, so it plugs into Voyager's standard service-provider and config-publish model. It is only relevant if your application already uses Voyager as its admin layer.
- How do I install monstrex/voyager-extension in a Laravel application?
- Installation follows the standard Laravel Composer flow: require the package, register the service provider, and publish its config and assets. Run any package migrations in a non-production environment first, then validate BREAD and admin routes. The biggest install risk is an unhealthy or partially upgraded Voyager 1.7 installation in the host app, so confirm that first.
- Which Laravel and Voyager versions does this package support?
- The current release line (0.95.84) explicitly targets Voyager 1.7 and Laravel 10, which implies PHP 8.1 or newer. It is unconfirmed whether Laravel 10 support is additive or a replacement for earlier majors, so verify the version matrix before planning an upgrade. Do not assume compatibility with Laravel 9 or below without checking.
- Does monstrex/voyager-extension work with Laravel 10 and Voyager 1.7?
- Yes, the v0.95.84 release notes explicitly reference Voyager v1.7 support and Laravel 10 targeting. The main caveat is that Voyager's own Laravel 10 support has its own version floors, so a mismatch between the installed Voyager minor and the one this package expects is the most likely breakage point. Confirm both versions match before deploying.
- Do I need to publish config and assets after installing?
- Yes, publishing the package's config and front-end assets is part of the normal install path for Voyager add-ons. When upgrading from an earlier 0.95.x release, diff your published config and asset files against the package's new stubs, since Voyager and Laravel support bumps often ship updated view or config defaults. Reconcile the differences manually rather than blindly overwriting.
- Are there database migrations I should worry about in production?
- The package may ship migrations if it persists BREAD definitions or settings, but the release notes do not state whether v0.95.84 includes schema changes. Take a database snapshot before running any migration and test the upgrade in a staging clone of production first. Deploy behind a maintenance window only if migrations are actually present.
- Is it safe to use a pre-1.0 (0.95.x) package in production?
- Pre-1.0 versioning means semver permits breaking changes in the minor position, so a jump to 0.96 could break consumers with no major-version signal. Pin to an exact version or a tight constraint like 0.95.* in composer.json. Treat it as a legacy-path dependency rather than a strategic one, and hold a rollback tag and database snapshot for at least one release cycle.
- How should I upgrade between 0.95.x releases of this package?
- Install the new version in a staging clone, diff published config and asset files against the package's new stubs, and reconcile any drift. Run your full test suite plus manual smoke tests on admin CRUD and BREAD screens. If migrations exist, snapshot the database first and deploy to production behind a maintenance window.
- What are alternatives to monstrex/voyager-extension?
- If you are not already committed to Voyager, greenfield Laravel projects are better served by Filament, Nova, or an Inertia-based admin stack. If you are on Voyager and only need a few helpers, Voyager's own hooks and custom form field types may be enough. This package makes the most sense for teams already standardized on Voyager 1.7 who want extra BREAD and form tooling without forking the admin layer.
- Who maintains monstrex/voyager-extension and how actively is it updated?
- The package is maintained by monstrex and tracks upstream Voyager and Laravel majors, which is the right posture for a glue package but couples its lifecycle to two upstream projects. Voyager itself has a slow release cadence, so long-term support is bounded by that ecosystem. Release notes for 0.95.84 mention only unspecified minor fixes, so check the repository changelog and issue tracker before relying on it.