- How do I install mrshanebarron/breadcrumbs in a Laravel app?
- Install it with Composer using composer require mrshanebarron/breadcrumbs, and pin the exact version while the package is early in its 1.x lifecycle. After installation, check composer.json for Laravel and PHP constraints, confirm whether package auto-discovery is enabled, and publish any config file if the package requires it. Run php artisan config:clear after publishing or changing configuration.
- Which Laravel and PHP versions does mrshanebarron/breadcrumbs support?
- The provided overview and v1.0.1 release note do not document supported Laravel or PHP versions. Check the package's composer.json constraints before installing, and test in a spike branch against your application's exact Laravel and PHP versions. Do not assume compatibility from the package name alone.
- How do I publish the breadcrumbs config file in Laravel?
- Use Laravel's vendor:publish command with the package's publish tag, then inspect the generated filename and contents. The v1.0.1 release fixed config file naming with an sb- prefix, so confirm you are publishing the current filename rather than a stale v1.0.0 artifact. If you previously published config, compare filenames, rename or delete and republish, then run php artisan config:clear.
- What does the sb- config prefix mean in this package?
- The sb- prefix appears in the v1.0.1 fix for config file naming, likely to namespace the package's published config file. Check that it does not collide with existing config names in your Laravel application. Also confirm the publish tag and target filename in the package source or documentation, because the release note does not explain what sb stands for.
- Can I build breadcrumbs from routes, URLs, and custom definitions?
- The package overview says it builds and renders breadcrumb trails from routes, URLs, or custom definitions. That gives you flexibility for route-driven navigation, manually defined URLs, or application-specific hierarchies. Verify the exact API methods in the package source or README after installation, since the provided README excerpt is empty.
- How do I render breadcrumbs in a Blade template with this package?
- The package is described as providing Blade-friendly output for hierarchical navigation. The exact Blade directive, component, or include syntax is not included in the provided README excerpt, so check the package's README or source after installation. Start with a simple route-based breadcrumb, confirm the rendered HTML, then adapt the markup to your layout.
- Is mrshanebarron/breadcrumbs safe to use with Laravel config caching?
- A conventional Laravel package that merges and publishes config should work with config:cache, but the config filename must be correct. The v1.0.1 config-name fix means a stale v1.0.0 published file could leave required settings unloaded if vendor:publish does not overwrite it. Clear and rebuild config cache after republishing, and smoke-test the breadcrumb output in a cached-config environment.
- What changed in v1.0.1 of mrshanebarron/breadcrumbs?
- The only documented change in v1.0.1 is a fix for config file naming using the sb- prefix. The release note does not state whether the v1.0.0 config filename remains supported or list other changes. If you adopted v1.0.0, compare your published config filename against v1.0.1 and republish or rename as needed before running config:clear.
- Should I pin mrshanebarron/breadcrumbs to an exact version?
- Yes, pinning to 1.0.1 is prudent while the package is very early in its 1.x lifecycle and its API stability, test coverage, and release cadence are unproven. Require the exact version in a spike branch, validate the primary breadcrumb paths, and only then consider widening the constraint. Assign an owner to review Composer updates and changelogs.
- What should I check before using mrshanebarron/breadcrumbs in production?
- Verify Composer constraints, auto-discovery, config publish tag, config filename, and config-cache behavior before production. Test the route, URL, and custom-definition breadcrumb paths in staging, including queue workers or long-running processes if the package is used there. Because maintenance and support are unproven, document the publish command, config filename, and rollback steps in your runbook.