Weave Code
Nav Bar Bundle Laravel Package
idci/nav-bar-bundle
A Symfony bundle that adds a configurable navigation bar to your application, letting you define menus, links, and routes in configuration and render them with Twig. Useful for centralizing site navigation and keeping templates free of hardcoded menu markup.
Symfony NavBarBundle
Frequently asked questions about Nav Bar Bundle
- Can I install idci/nav-bar-bundle in a Laravel application?
- No. It is a Symfony2 bundle, not a Laravel package, and Laravel does not implement the Symfony bundle contract. Composer will also fail because the bundle pins Symfony 2.x constraints while Laravel requires Symfony 6 or 7 components. There is no service provider, middleware, or Blade integration path.
- Does idci/nav-bar-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony2, which reached end of life in November 2018. Laravel 10 and 11 depend on Symfony 6/7 components and PHP 8.1+, so the version constraints cannot resolve together. A Blade component is the correct replacement.
- Is idci/nav-bar-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle (idci/nav-bar-bundle) for building configurable navigation bars. It integrates with Symfony routing and Twig templating, not Laravel's router or Blade. It is mis-catalogued if listed under Laravel tooling.
- How do I install idci/nav-bar-bundle?
- In a Symfony2 application you would run composer require idci/nav-bar-bundle and register the bundle in AppKernel. That is the only supported installation path. In Laravel, composer require will fail at dependency resolution, so there is nothing to configure.
- Is idci/nav-bar-bundle still maintained?
- No meaningful maintenance is evident. It has zero stars, zero dependents and zero forks, and targets an end-of-life Symfony generation. There is no upstream to inherit fixes from, so a fork would make you the sole maintainer. Treat it as abandoned for any new work.
- What does idci/nav-bar-bundle actually do?
- It models navigation items with labels, routes or URLs, and supports nested or grouped entries. Templates render those items through Twig helpers. The result is a config-driven static menu tree, not a database-backed CMS. The core is a menu item tree plus recursive rendering, which is only a few hundred lines.
- Will idci/nav-bar-bundle work on PHP 8.2?
- Unlikely. Symfony2-era code is untested above PHP 7.x and will often fatal or emit loud deprecations on PHP 8.2+. Since PHP 8.1+ is the supported floor for current Laravel, this is a blocking compatibility issue rather than a cosmetic one.
- What is the best Laravel alternative for a configurable navigation bar?
- Build it in-house: a Menu and MenuItem value object plus a recursive Blade component. Resolve active state with request()->routeIs() and authorize items through Laravel gates or policies at render time. If menus must be editable at runtime, back them with menus and menu_items tables and cache the resolved tree. This is a one-to-two day build that you fully own.
- How do I render nested navigation menus in Blade?
- Use a recursive Blade component such as <x-nav.menu :items="$items" />. The component loops over items, renders label and URL, and includes itself for any children. Pass an active flag and optional icon or attributes per item. Cache the resolved tree if it comes from the database.
- How do I test a navigation bar in Laravel?
- Test the tree builder and the renderer separately. Unit test menu item resolution and active-state predicates, then use feature tests or snapshots to assert the Blade component output. Define test routes so request()->routeIs() returns predictable active states. No Symfony bundle is needed for any of this.
Weaver
How can I help you explore Laravel packages today?