- Does this package support Laravel 10 and Laravel 11?
- Laravel 10/11 support is not confirmed: the last release was March 2022, so the existing Composer constraints may not match current PHP or Blade versions. Validate the constraint set against your target matrix and run a short install-and-render spike before committing. If component discovery or rendering fails, vendoring the small MIT-licensed component into your app is a realistic fallback.
- How do I install leuverink/blade-shape-divider in a Laravel app?
- Install it with Composer using composer require leuverink/blade-shape-divider. The package registers its Blade component through auto-discovery, so you can render a divider with a single component tag and props. A first working divider should take under an hour for a developer familiar with Blade.
- What props can I pass to the Blade shape divider component?
- The component exposes simple props for shape, color, height, flip or invert, and position. Those props let you place a divider above or below a section and tune its look without copying SVG markup. Confirm exact prop names in the README before standardizing them in your design system.
- Does the shape divider work without Tailwind CSS?
- Yes. The package renders SVG shape dividers and does not depend on Tailwind or another CSS framework to function. You can align colors and heights with your design tokens through props, and wrap the component if you need project-specific defaults.
- Is the SVG output accessible to screen readers by default?
- Decorative dividers should not be announced by assistive technology, so the rendered SVG should include aria-hidden=true or role=presentation. The technical assessment flags that accessible-by-default output is unverified. Inspect the actual markup in your spike and add the attributes in a wrapper or published view if they are missing.
- Is it safe to pass user input to color or height props?
- Only pass trusted values to props such as color and height. If the component interpolates props into SVG attributes without escaping, arbitrary user input could become an XSS vector. Validate and whitelist values, and never feed raw request data into the divider component.
- Does it output inline SVG or reference an external file?
- The package renders inline SVG through Blade, which keeps the divider self-contained but adds markup to the HTML payload. Check the output size and your Content Security Policy implications during the spike. Inline SVG is generally fine for a handful of dividers per page.
- Can I use it with Livewire or Inertia?
- It fits server-rendered Laravel and Blade-heavy stacks, including Livewire apps that render Blade components. In an Inertia app it is only relevant where server-side Blade renders the layout shell; it does nothing for client-only rendering paths. It is not intended for API-only or headless backends.
- Is the package actively maintained, and what if it is abandoned?
- Treat it as effectively unmaintained: the last release was March 2022, there is a single maintainer, and there are no dependents. Pin the version, name an owner, and wrap it in a first-party component so the dependency appears in one place. Because the code is small and MIT licensed, forking or replacing it in-house is low risk.
- How do I customize divider colors, heights, or views for my design system?
- Start by using props to match your design tokens for color and height, then publish or override views only if you need structural changes. Wrap the package in an application-owned component such as x-app.divider so upgrades or a fork touch one file. Add a snapshot or visual regression test to catch breakage during Laravel upgrades.