Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Menus

Laravel Menus Laravel Package

nwidart/laravel-menus

Laravel Menus is a flexible menu builder for Laravel apps. Define menus and nested items in code, add links or routes, control ordering and active states, and render them with built-in or custom presenters. Supports Bootstrap-style markup and view partials for quick, maintainable navigation.

View on GitHub
Deep Wiki
Context7

Laravel Menu Management

Frequently asked questions about Laravel Menus
How do I install nwidart/laravel-menus in a Laravel app?
Install the package with Composer using nwidart/laravel-menus, then follow the package documentation for any service provider or configuration publishing steps. Before installing, check the composer.json constraints to confirm the package supports your Laravel and PHP versions. Run your application test suite after installation to catch integration issues early.
Does nwidart/laravel-menus support Laravel 8?
The 7.0 release note states that Laravel 8 support was added. The exact illuminate/support constraint and whether Laravel 6 or 7 remain supported are not confirmed in the supplied evidence. Verify composer.json and the changelog before assuming compatibility with your framework version.
How do I define menus and nested items in code with Laravel Menus?
Laravel Menus is designed for defining menus and nested items in code rather than only in database records. You can build item hierarchies, attach links or routes, and control ordering through the package API. Check the package documentation for the exact builder methods and naming conventions.
How do I add a route link to a menu item?
The package supports adding links or routes when defining menu items. Use the menu builder API to attach the route or URL, then render the menu through a presenter or view partial. Confirm the exact route method names in the package docs for your installed version.
How are active menu states handled in nwidart/laravel-menus?
Laravel Menus includes support for controlling active states when rendering navigation. Active state behavior is typically tied to the current request or route and is applied by the presenter. Test the rendered output in your own application to confirm the active classes match your routing setup.
Can Laravel Menus render Bootstrap-style navigation markup?
Yes, the package supports Bootstrap-style markup through its built-in presenters. You define the menu structure in code and let the presenter output the appropriate navigation HTML. If the default markup does not fit your design system, you can use a custom presenter instead.
Can I use custom presenters or view partials to render menus?
Laravel Menus supports built-in and custom presenters as well as view partials for rendering. This lets you keep menu definitions in code while controlling the final HTML output. Custom presenters are useful when your application uses Tailwind, custom CSS classes, or non-Bootstrap markup.
Is nwidart/laravel-menus 7.0 a breaking change I need to plan for?
Version 7.0 is a major release whose available release note only mentions Laravel 8 support. That does not prove there are no incidental breaking changes, so review composer.json, diff any published configuration, and run your test suite before upgrading. If your application is on Laravel 6 or 7, confirm whether 7.0 still supports those versions or forces a framework upgrade.
How should I test menus built with nwidart/laravel-menus?
Test the rendered HTML rather than only the menu definition objects. Feature tests can assert item order, nested structure, route URLs, and active state classes in the final output. Since package-level test coverage details were not supplied, also check the repository CI configuration for supported Laravel and PHP combinations.
Is nwidart/laravel-menus actively maintained and safe for production?
The 7.0 release confirms the package is alive, but the supplied evidence does not establish release cadence, responsiveness, or bus factor. Before production adoption, check the repository history, open issues, CI matrix, and upgrade guides. Also verify that the package constraints align with your Laravel and PHP runtime before committing.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo
bernskioldmedia/laravel-harvest
bernskiold/laravel-data-scrubber
bernskiold/laravel-currency-converter
bernskiold/laravel-campaign-monitor
bernskioldmedia/laravel-autotranslate
siberfx/telegram-bot
roy-sandip/laravel-view-extended
gregsphotography/site-builder-core
roy-sandip/laravel-view
anodyne/blade-fluentui-icons
webx-ui/module-catalog-collections