Weave Code
Breadcrumbs Laravel Package
wireui/breadcrumbs
A Laravel Blade breadcrumbs component for WireUI apps that renders accessible navigation trails with icons, links, and active-page states. Simple configuration makes it easy to build breadcrumb paths in your views with minimal markup.
Breadcrumb component for Laravel, Livewire, TallStack
Frequently asked questions about Breadcrumbs
- How do I install wireui/breadcrumbs in a Laravel app?
- Install it with Composer using composer require wireui/breadcrumbs. Laravel package auto-discovery registers the service provider, and there are no migrations, environment variables, queue workers, or scheduled tasks to configure. You can optionally publish configuration or views if you need to customize the component. Then render the breadcrumbs component in your Blade layouts.
- Does wireui/breadcrumbs support Laravel 12?
- Laravel 12 support arrived in v3.3.0 through a community pull request, so pin ^3.3 as the minimum viable version for a Laravel 12 target. Before upgrading, run composer why-not laravel/framework 12 to confirm no other pinned dependencies block the framework bump. Also verify that the package's CI matrix actually exercises Laravel 12, not just relaxed version constraints.
- Do I need WireUI or Livewire to use this breadcrumbs package?
- The package is built for the WireUI ecosystem and is Livewire-friendly, so it fits naturally if you already use those tools. It is a single-purpose Blade component and does not add persistence, service layers, background work, or external I/O. If you are not using WireUI, it can still stand alone, but it assumes Tailwind-based styling conventions. It is not suitable for API-only services or non-Blade SPAs.
- How do I customize breadcrumb separators, icons, and active-page styling?
- The package exposes a simple PHP and Laravel API for defining breadcrumb items, with customizable separators, icons, link behavior, and active-page states. Start with the default component usage, then publish or override the Blade views if your design system needs different markup or classes. Because styling is Tailwind-based, customize with utility classes and confirm your overrides survive production builds.
- Can I publish and override the breadcrumb Blade views?
- The package is designed as a Blade component with optional view publishing, so you can override markup to meet your design system and accessibility standards. Use this to ensure output includes semantic navigation such as a nav element with an aria-label, an ordered list structure, and aria-current for the active page. Validate the emitted HTML against your accessibility checklist before rolling it out across layouts.
- Why are my wireui/breadcrumbs styles missing in production?
- Tailwind may be purging the package's classes if its view directory is not included in your content globs. After installing, confirm your Tailwind content configuration includes the package's view paths so production builds retain the required utility classes. Test a production build, not only local development, because unstyled breadcrumbs often appear only after purging.
- Are breadcrumb labels escaped by default, and can I render raw HTML?
- Breadcrumb labels should be treated as escaped output by default, which is important when labels derive from route parameters or other user-controlled data. Before adoption, confirm the component's escaping behavior and whether it exposes a raw-HTML slot or escape hatch. Avoid passing unescaped user input into any raw slot, and use escaped labels for dynamic route values.
- Can I use wireui/breadcrumbs in an Inertia, Vue, or React front end?
- No, this is a server-rendered Laravel Blade component, so it is not applicable to Inertia, Vue, or React front ends where breadcrumbs must be implemented client-side. Scope adoption to Blade layouts and Livewire-driven pages. For API-only services or non-Blade SPAs, use a client-side breadcrumb solution instead.
- How do I build dynamic breadcrumb trails from route parameters?
- Define breadcrumb items through the package's PHP and Laravel API, passing labels and URLs based on the current route or model context. Keep dynamic labels escaped, and test trails with two levels, deep nesting, and parameter-driven pages. If you need reactive updates in Livewire pages, confirm your component usage reflects the current route state correctly.
- Is wireui/breadcrumbs actively maintained, and what are the alternatives?
- It is a small, narrowly scoped open-source project with a low release cadence, so assess issue-response history and tagged releases before adoption. The tiny code surface makes forking or vendoring cheap if maintenance slows. Alternatives include an in-house Blade partial for full control or a client-side solution for non-Blade front ends. Expect MIT licensing, but verify the license file in the repository.
Weaver
How can I help you explore Laravel packages today?