- What is biostate/filament-menu-builder used for?
- It is a Filament panel plugin for building and managing nested navigation menus visually. You can create drag-and-drop menus, add custom links or model-based items, reorder entries, and render configurable menus in a Laravel application. It fits Laravel and Filament stacks where menus would otherwise be hard-coded or stored as a simple parent_id tree.
- How do I install biostate/filament-menu-builder?
- Install it with Composer using composer require biostate/filament-menu-builder, then register the plugin on your Filament panel. The package uses conventional integration surfaces: published migrations and configuration plus a nested-set-enabled model. Check the repository README for the exact plugin registration class and publish commands for your version.
- Which Laravel and Filament versions does it support?
- The v5.1.0 release targets Laravel 11+ with Filament v5 and PHP 8.2+, with PHP 8.3+ required for Laravel 13. Laravel 11 and 12 resolve kalnoy/nestedset v6, while Laravel 13 resolves nestedset v7. Filament v4 and earlier are outside the tested support envelope, so confirm the Filament floor before adopting.
- How do I register the plugin in a Filament panel?
- Registration follows the normal Filament plugin pattern: add the package's plugin class to your panel configuration. v5.1.0 drops manual BladeCaptureDirectiveServiceProvider registration, reflecting a hard dependency on Filament v5 behaviour. Use the plugin class named in the repository documentation rather than copying older v4-era setup snippets.
- How does biostate/filament-menu-builder store nested menu data?
- It is backed by kalnoy/nestedset, so menu records use nested-set columns such as _lft, _rgt, parent_id, and depth. That supports efficient hierarchical queries and tree operations instead of a naive parent_id-only structure. Existing v6-backed data should be checked against nestedset v7 behaviour before moving to Laravel 13.
- Can I add custom links and model-based menu items?
- Yes. The package lets you add custom links or model-based items to a menu and reorder entries through the drag-and-drop Filament UI. This makes it suitable for mixed navigation that includes both static URLs and records from your application models. Confirm the exact item types and configuration options in the package source for your version.
- How do I render the built menu in Blade?
- The package is designed to integrate configurable menus into your Laravel app and render them into Blade or other front-end output. Menus are persisted as nested-set records, so your rendering layer reads that hierarchy rather than hard-coded navigation. The provided context does not document exact Blade helpers or components, so verify the rendering API in the repository before implementation.
- Is upgrading from 5.0.4 to 5.1.0 safe?
- v5.1.0 is a minor release with no data migration, no config key renames, and no published-asset changes. Its only runtime change is a widened Composer constraint; Laravel 11 and 12 installs still resolve nestedset v6 and should be unaffected at runtime. The Laravel 13 path is supported by constraint but should be exercised in CI before production.
- Does it work with Laravel 13 on PHP 8.2?
- No. Laravel 13 requires PHP 8.3 or higher, and PHP 8.2 is excluded from the Laravel 13 matrix, so PHP 8.2 plus Laravel 13 is an unsupported combination. v5.1.0 resolves the Laravel 13 and nestedset v7 install conflict reported in issue #31, but you should enforce the PHP floor in CI. Treat the Laravel 13 path as supported by constraint and unproven until tested in your codebase.
- What should I check before using this package in production?
- Verify the supported Filament range, nestedset v7 breaking changes and migration notes, and whether Laravel 13 is tested against GA or a pre-release branch. Review the regenerated PHPStan baseline to confirm it reflects the larastan 3 and PHPStan 2 toolchain rather than hiding new findings, and check whether coverage is still collected after the pcov driver change. Also assess maintainer activity, bus factor, and release cadence because the available assessment is based on release notes only.