Weave Code
Breadcrumbs Laravel Package
arcanedev/breadcrumbs
ArcaneDev Breadcrumbs is a Laravel package for defining and rendering flexible breadcrumb trails. Build crumbs from routes, closures, or arrays, customize templates, and output accessible navigation with minimal setup.
Arcanedev Breadcrumbs is a flexible Laravel package for defining and rendering breadcrumb trails. It separates breadcrumb generation from presentation, letting you register named trails via a simple manager and output them with a variety of built-in renderers.
- Define breadcrumbs fluently through the Breadcrumbs manager or dedicated generator classes
- Ship with multiple view renderers (Bootstrap, Bulma, Foundation, Materialize) and support for custom templates
- Integrate cleanly with Laravel service providers and facades
- Handle multilingual labels and dynamic route-based links with ease
Frequently asked questions about Breadcrumbs
- How do I install arcanedev/breadcrumbs in a Laravel app?
- Install it with Composer using composer require arcanedev/breadcrumbs, then confirm the package's service provider is discovered or registered according to the version's docs. Check composer.json constraints for Laravel and PHP before installing, because the 6.x line is a major version and may not match older framework pins. Publish any config or view assets only if you need to customize the defaults.
- Which Laravel and PHP versions does arcanedev/breadcrumbs support?
- The provided context does not list exact constraints, so verify laravel/framework, illuminate/*, and php requirements in the package's composer.json before adoption. Version 6.0.1 is a patch on the 6.x major line, so the 6.0.0 changelog and upgrade guide are the relevant compatibility artefacts. Do not assume support for older Laravel majors without checking the CI matrix.
- How do I create breadcrumbs from a Laravel route?
- Define a breadcrumb trail that references the route name, then let the package resolve the route URI and label when rendering. This keeps breadcrumb definitions close to your route names and avoids hard-coding URLs. Confirm the exact API in the package docs for your installed version.
- Can I define breadcrumbs with a callback or an array?
- Yes, arcanedev/breadcrumbs supports building trails from routes, callbacks, and arrays. Callbacks are useful when labels or URLs depend on request data, while arrays work for static trails. Keep dynamic definitions in a service provider or dedicated breadcrumbs file so they are easy to test.
- How do I render breadcrumbs in Blade?
- Render the trail in Blade using the package's documented helper or directive, then style the output through its customizable templates. The package integrates with Laravel views, so you can publish and override templates if the default markup does not match your design. Verify the exact Blade syntax against the 6.x docs.
- Does arcanedev/breadcrumbs support multiple breadcrumb collections?
- Yes, the package supports multiple collections, which lets you maintain separate trails for different sections of an application. Use distinct collection names when defining and rendering so each trail resolves independently. This is useful for admin, storefront, and documentation areas in the same Laravel app.
- How do I customize the breadcrumb HTML template?
- Publish the package views or point the renderer at your own template, then adjust the markup and CSS classes to match your front end. Because the package renders through Laravel's view layer, customization stays in Blade rather than in package code. Recheck overrides after upgrading the 6.x line in case template expectations changed.
- Is arcanedev/breadcrumbs suitable for production use?
- It can be, but treat 6.0.1 as an adoption of the 6.x major line, not a standalone patch. Before production, verify the composer constraints, test suite and CI coverage, release cadence, and the 6.0.0 upgrade notes. Pin the version and record published config, views, and service-provider registration as your rollback inventory.
- How should I test breadcrumbs in a Laravel application?
- Write feature tests that call the routes which define breadcrumbs and assert the rendered HTML contains the expected labels and links. Unit-test callback and array trail definitions separately so label logic is covered without a full request. Use Laravel's standard response assertions rather than coupling tests to package internals.
- What are alternatives to arcanedev/breadcrumbs?
- Common alternatives include diglactic/laravel-breadcrumbs and older davejamesmiller/laravel-breadcrumbs forks, though you should compare their supported Laravel versions and maintenance status. Evaluate alternatives on rendering templates, multiple collections, route integration, and upgrade cadence. If your app already uses Blade components, a small custom breadcrumb builder may also be simpler than adding a dependency.
Weaver
How can I help you explore Laravel packages today?