Blade Laravel Package

Product Decisions This Supports

• Icon rendering consistency across surfaces: v2.0.1 fixes a real visual defect where overriding stroke width on <x-solar-*> components or via svg() emitted a duplicate stroke-width attribute. If your product surfaces icons in multiple densities (dense data tables, marketing headers, mobile nav), this removes per-surface CSS hacks and inconsistent icon weight.
• Build vs. buy: Confirms the case for staying on this package rather than hand-rolling an SVG pipeline. The maintainers are actively correcting the rendering contract (single source of truth for stroke width in config), which is exactly the grunt work you don't want your team owning.
• Roadmap input — asset export workflows: The behavioral change matters if your roadmap includes publishing SVGs as static assets (email templates, CMS content, CDN-served icons, design handoff). Those published files now ship without a baked stroke-width and render at the SVG default when used standalone. Any roadmap item depending on published assets must budget for an explicit stroke-width at the point of use.
• Theming and design tokens: Stroke width moving to package config is a step toward token-driven iconography. It opens the door to per-brand/per-tenant stroke weights set once in config rather than patched per component — useful if you support white-label or multi-brand surfaces.
• QA scope decisions: This is a low-risk patch for teams using icons exclusively through Blade components, but a verify-before-ship item for teams that publish raw assets. That distinction should drive whether this is a routine dependency bump or a release-gated change.

When to Consider This Package

Adopt (or stay) when:

• You render icons through Blade components (<x-solar-*> or svg()) and want stroke width controlled centrally via package config rather than per-call overrides.
• You've been fighting duplicate attributes or specificity conflicts when overriding stroke weight — this release targets exactly that.
• You want a maintained, config-first icon set over a bespoke sprite/SVG build.

Look elsewhere or proceed carefully when:

• You publish raw SVGs as assets and consume them outside Laravel (email, static CDN, third-party CMS, design tools). Post-upgrade, those files have no baked stroke-width and will render thinner than intended at the SVG default. Either keep the previous version pinned for the asset pipeline, or add explicit stroke width at the consumption layer.
• You need multi-weight icons (duotone, filled, mixed stroke/fill families) where a single global stroke-width config is the wrong abstraction.
• Your icon contract is locked by visual regression tests against the old baked-attribute output — expect snapshot churn.
• You require a formal deprecation/semver policy; note this shipped as a patch (2.0.1) despite changing the rendered output of published assets. Treat it as behaviorally breaking and read the diff, not the version number.

Adoption criteria: pin the version, run a visual regression pass on both component-rendered and published-asset icons, and confirm every standalone SVG consumer sets stroke width explicitly.

How to Pitch It (Stakeholders)

For executives: A small, targeted fix from an actively maintained dependency. It removes a class of icon-rendering bugs caused by duplicate stroke-width attributes and centralizes icon weight in configuration — less custom CSS, fewer visual inconsistencies across the product, lower maintenance cost. Cost is a routine version bump plus a short QA pass.

For engineering: Upgrade to 2.0.1. Stroke width is now applied once, from package config, instead of being baked into every file — fixing the duplicate stroke-width you get when overriding weight on a static <x-solar-*> component or via svg(). Caveat: raw SVGs published as assets no longer carry a baked stroke-width; used standalone they fall back to the SVG default. Audit anything that consumes published SVGs outside Blade and set stroke width explicitly there. Add visual regression coverage for both paths before rollout; expect snapshot updates.