Weave Code
Laravel Navigation Laravel Package
fuelviews/laravel-navigation
FuelViews Laravel Navigation offers a simple, configurable way to build and manage dynamic navigation menus in Laravel. Define menus and links, then render them cleanly in Blade views with minimal setup.
Laravel navigation package
Frequently asked questions about Laravel Navigation
- How do I install fuelviews/laravel-navigation in a Laravel application?
- Install it with Composer using composer require fuelviews/laravel-navigation and pin the ^2.0 constraint. It is a standard Laravel package with service provider auto-discovery, so no manual registration is required. Publish the config file on day one so you own the defaults instead of inheriting them from upstream. After that, add the render call to your layout Blade file.
- Does laravel-navigation support multiple menus?
- The package is described as a simple, configurable way to define menus and links, and the 2.0.5 release notes do not document a single-menu limit. Confirm multi-menu support against the config schema in the version you install before designing around it. If your app needs per-user or dynamic menus, verify that too, since there is no evidence of a database-backed menu model in this release.
- How do I publish and override the package configuration?
- Run php artisan vendor:publish and select the laravel-navigation config tag, then edit the published file in your config directory. Do this before going to production, because 2.0.5 changed a default phone number value and any app relying on the shipped default will render different output without a code diff. Owning the config makes those upstream default changes explicit and reviewable.
- Which Laravel and PHP versions does this package support?
- The supported range is declared in the package composer.json, and 2.0.5 also pins several dependencies to specific versions for stability. Check those bounds against your oldest supported Laravel app and your lockfile before upgrading, since pinned constraints can create Composer resolution conflicts on older Laravel majors. If you maintain more than one Laravel major, test constraint resolution in each.
- How do I render a navigation menu in a Blade view?
- Navigation output is server-rendered markup, so you typically include the package's Blade partial or render call inside your layout. The exact call depends on the API exposed by the version you install, so check the README or published views first. Because output is plain HTML, it works in any Laravel app regardless of frontend stack.
- Does laravel-navigation support active states and nested submenus?
- The package renders menus and links from config, and active-state highlighting is common with this pattern, but the 2.0.5 notes do not enumerate nesting or active-state behavior. Verify both against the config schema and rendered output in staging. If nesting is unsupported, you may still model it through multiple menu definitions once multi-menu support is confirmed.
- Can I cache the navigation menu in production?
- There is no documented cache key or invalidation story in this release, so treat caching as something you implement rather than something the package provides. Since menus are config-driven, standard Laravel config caching applies to the config itself, and you can wrap the render call in your own cache directive. Confirm the Blade partial does not depend on per-request state before caching rendered output.
- Does laravel-navigation support permission-based menu visibility?
- There is no evidence in this release of a permission-aware menu model, so do not assume per-user visibility out of the box. The package is a presentation-layer, config-plus-Blade dependency and does not own auth or persistence concerns. If you need role-based menus, gate links in your own Blade wrapper or filter the config before rendering.
- Is v2.0.5 a breaking change from v2.0.4?
- It is a patch bump with no declared breaking changes, no new public API, and no deprecations, so apps on 2.0.4 just run composer update inside the existing ^2.0 constraint. The caveats are behavioral rather than semver: route names and URIs were corrected and a default phone number changed in config. Grep your app and tests for hardcoded route names and route() calls before merging.
- Can I use this package with Inertia or Livewire frontends?
- Output is server-rendered Blade markup, so Inertia and Livewire teams can use it only if they can render the Blade partial or share the same config and re-implement rendering. Confirm the rendering contract for your version before committing to it. Teams already standardized on Laravel config-plus-Blade idioms get the lowest-friction fit.
Weaver
How can I help you explore Laravel packages today?