Lucide For Laravel Laravel Package

Product Decisions This Supports

• Icon/UI work is no longer a design-blocking dependency. A v2.4.0-style drop adds 32 new glyphs (finance/locale symbols like armenian-dram, bangladeshi-taka, kazakh-tenge, nepali-rupee; domain icons like printer-3d, faucet, cupcake, rugby-ball; text/alignment and square-dashed-* variants). For a PM this means "we need an icon for X" is a composer bump, not a design ticket or a custom SVG commit — it removes a recurring, low-value interrupt from the sprint.
• Localisation and market expansion get cheaper. The currency-glyph cluster is a direct signal that per-market symbol requirements (dashboards, invoicing, pricing tables) can be met without bespoke assets. If we are planning entry into any of those markets, budget the icon dependency as already solved rather than a scoping risk.
• Build vs buy: this is a thin wrapper over the upstream lucide-static set, exposing a Lucide enum plus Blade rendering (@svg('lucide-…')). That is a buy/adopt decision, not a build one — we are buying curation, enum ergonomics, and a maintained sync pipeline, not glyph design. Building in-house would mean owning exactly the bump → sync → test → PR grind this package has already automated (ADR-0009).
• Supply-chain hygiene is a product argument, not just an engineering one. The automated regeneration-plus-Pest-gate pipeline is evidence the dependency will not silently rot. That lowers the "will this be abandoned/half-synced in 12 months" risk that normally makes PMs nervous about small third-party UI packages.
• Roadmap signal for icon-dependent features: because the icon set is pinned to lucide-static within ^1.x, upstream additions arrive on a lag and only via package releases. Do not commit a roadmap item that depends on a specific upstream icon existing until it is present in the enum.
• Redraws are a real (small) product cost. The 8 changed glyphs (broccoli, card-sim, mail-pen, map-pinned, nut, nut-off, save-off, calendar-chevrons-right) keep their names but change paths. Pixel-level visual diffs will appear in screenshot tests and design reviews; nobody needs to change code, but someone needs to not file a bug.

When to Consider This Package

Adopt when:

• The product is Laravel/PHP and the front end already renders icons via Blade — the @svg('lucide-…') + Lucide::Case pairing gives typed, greppable, autocompletable icon references instead of magic strings.
• The design language tolerates or prefers an open, consistent stroke-icon set, and you want one canonical source of truth rather than ad-hoc SVGs per feature.
• You want icon upgrades to be cheap and boring: this release is explicitly purely additive — no glyphs renamed or removed, so a v2.3.0 → v2.4.0 bump carries no migration work.
• You value a tested dependency: the package regenerates its tree and runs a Pest suite against it on every upstream bump.

Look elsewhere or hold when:

• You need filled/duotone/multi-colour iconography, or brand- or illustration-led visuals — Lucide is a single consistent outline style.
• You are not on Laravel, or you render icons primarily client-side; the enum + Blade ergonomics are the main value and you would be paying for a wrapper you do not use.
• You depend on a specific new upstream icon today — check the enum first. Availability lags upstream via the pinned ^1.x range.
• You require guaranteed semver discipline across enum case names. Treat names as an API you verify, not one you derive: printer-3d maps to Lucide::PrinterThreed (digits spelled out). Any codegen, docs, or Figma-to-code mapping that assumes a mechanical kebab→PascalCase transform will break on cases like this — assert against the real enum rather than generating names.
• Your release process gates on visual snapshots without a tolerance budget; redraw-only releases will generate noisy diffs.

How to Pitch It (Stakeholders)

To executives: We get a professionally maintained, actively synced icon library for free, wired into our existing Laravel code. Version 2.4.0 adds 32 icons — including currency symbols for several target markets — and changes nothing that breaks us. It is a low-risk, zero-migration upgrade, and the project's automated release pipeline means we are not taking on a dependency that quietly decays.

To engineering: Purely additive release. 32 new icons, 8 upstream redraws (same names, same enum cases), zero removals. Nothing to change when upgrading from v2.3.0 — bump the constraint, run the suite, and expect only screenshot-diff noise on the redrawn glyphs. Two things to note: use the enum (Lucide::…) as the source of truth rather than deriving case names from icon slugs (PrinterThreed proves the mapping is not mechanical), and remember new icons arrive only when the package bumps its pinned lucide-static range. The bump → sync → test → PR automation from ADR-0009 is why we can take these bumps on a routine cadence instead of batching them into risky upgrades.