Weave Code
Breadcrumbs Bundle Laravel Package
lafourchette/breadcrumbs-bundle
A Symfony bundle for building and rendering breadcrumb trails. Define breadcrumbs through service configuration or annotations, then display them in Twig templates with minimal setup for consistent navigation across your application.
A simple breadcrumbs bundle
Frequently asked questions about Breadcrumbs Bundle
- Is lafourchette/breadcrumbs-bundle a Laravel package?
- No. It is a Symfony bundle: the Bundle suffix, DependencyInjection extension layout and Twig extension integration are all Symfony conventions, so it cannot be composer required into a Laravel app and used as intended. There is no documented Laravel service provider, facade or adapter. If you are building in Laravel, treat this package as out of scope and pick a Laravel-native breadcrumb solution instead.
- Can I install lafourchette/breadcrumbs-bundle in a Laravel application?
- Composer may resolve it, but Laravel has no Symfony kernel or bundle registration lifecycle, so the breadcrumb services and Twig extension will never boot. Building a compatibility shim would cost more effort than writing a small trail service and Blade partial yourself. For a Laravel target this package should be rejected on framework fit alone.
- How do I install and configure lafourchette/breadcrumbs-bundle in Symfony?
- Composer require the package, register it in config/bundles.php, and optionally add YAML configuration for your trails. Trails can be defined through service configuration or annotations, then rendered in Twig with a single call in your base layout. Budget roughly half a day including environment setup for a typical Symfony app.
- Does lafourchette/breadcrumbs-bundle support modern Laravel versions such as Laravel 10 or 11?
- It supports no Laravel version at all because it is a Symfony bundle, not a Laravel package. Even in Symfony, the package is old enough that its composer.json likely caps PHP at 7.x and Twig at 1.x or 2.x, which conflicts with modern runtimes. Check the actual constraints before assuming it installs cleanly anywhere current.
- What is a good Laravel alternative to lafourchette/breadcrumbs-bundle?
- Use a maintained Laravel-native option such as diglactic/laravel-breadcrumbs, which ships a service provider, facades and Blade rendering. Avoid the archived davejamesmiller lineage as well. For very small apps, a Blade partial plus a simple trail service is often enough and avoids another dependency entirely.
- Is lafourchette/breadcrumbs-bundle actively maintained?
- No. It has zero stars, zero dependents and effectively no community surface, so expect no upstream fixes, security triage or compatibility work for modern PHP and Twig. Check the last commit date and whether the repository is archived before committing to it. For a production Laravel app this level of abandonment is a hard blocker.
- How do I render breadcrumbs in Twig using lafourchette/breadcrumbs-bundle?
- Once the bundle is registered in a Symfony kernel, you add a single breadcrumb render call to your base template and the bundle's Twig extension outputs the trail. Trail nodes are label and URL pairs built from your service configuration or annotations. There is no equivalent Blade directive, so this render step does not translate to Laravel.
- Will lafourchette/breadcrumbs-bundle work on PHP 8.2 and Twig 3?
- Probably not without changes. The package is from the Symfony 2.x and 3.x era and its constraints likely cap PHP at 7.x and Twig at 1.x or 2.x, so Composer resolution may fail or you may see deprecations at render time. Verify the composer.json constraints and test in staging before relying on it.
- Should I fork or vendor lafourchette/breadcrumbs-bundle instead of requiring it?
- The breadcrumb logic is genuinely small, so vendoring the source into an internal namespace and dropping the stale composer constraints is a reasonable option if you must stay on Symfony. Pin an exact version and commit composer.lock rather than floating the constraint. Confirm the license first, since vendoring or forking must fit your policy.
- What are the risks of depending on an unmaintained breadcrumbs bundle?
- Functional risk is low because breadcrumb generation is trivial, but abandonment risk is high with no fixes, no security triage and no compatibility work. Supply chain risk is medium because old transitive dependencies are a bigger exposure than the breadcrumb code itself. Keep trails defined in one config map keyed by route name so swapping implementations later touches a single file.
Weaver
How can I help you explore Laravel packages today?