Tabler Ux Components Laravel Package

Product Decisions This Supports

• Icon strategy and design-system roadmap: v0.8.0 lets Icon and every icon prop accept prefixed Symfony UX Icons names (lucide:circle-check, mdi:account, tabler:check), rendering inline <svg> while preserving existing variant, size, animation, and Tabler icon classes. PMs can now plan a multi-icon-set design system without replacing the component layer.
• Build vs. buy: The package already supplies Twig-native Tabler components with consistent icon APIs. This release removes a common reason to build a custom icon abstraction just to mix icon sets or move from webfont to inline SVG.
• Feature and migration decisions: Teams can adopt prefixed SVG icons incrementally. Unprefixed names still use the Tabler webfont, so existing screens do not need a flag-day migration.
• Use cases to prioritize: Admin panels, dashboards, and internal tools built on Tabler/Tailwind where product wants Lucide, MDI, Tabler, or mixed icon sets; accessibility- or performance-sensitive surfaces where inline SVG is preferred; brands standardizing on a non-Tabler icon set while keeping Tabler UI components.
• Dependency and packaging decisions: Prefixed SVG icons require symfony/ux-icons (now suggested). PMs should decide whether to add that dependency for teams that want inline SVG, while keeping webfont fallback for teams that do not.
• Release hygiene: The Symfony UX Toolkit kit now requires @tabler/icons-webfont 3.36.1+ for filled icons used by <twig:Tabler:Icon filled>. This is a frontend asset pin to verify in upgrade planning, not a breaking API change.

When to Consider This Package

• Adopt when the product is on a Symfony UX / Twig Components stack and uses Tabler-based UI, and the team wants Twig-native components rather than assembling Tailwind/Tabler markup by hand.
• Adopt when icon flexibility matters: product or design wants to standardize on Lucide, MDI, Tabler, or a mix, and the team values a single Icon API with consistent sizing, variants, and animation classes.
• Adopt when incremental migration is important: unprefixed names continue to use the Tabler webfont, so teams can test prefixed inline SVG on selected surfaces before broad rollout.
• Adopt with caution when adding symfony/ux-icons is undesirable. The feature is opt-in, but teams wanting prefixed SVG icons must accept that dependency.
• Look elsewhere when the product is not on Symfony/Twig, needs a React/Vue component library, requires a non-Tabler visual system, or cannot manage frontend asset version pins such as @tabler/icons-webfont 3.36.1+.
• Look elsewhere when the team requires a fully custom icon pipeline, sprite-sheet-only delivery, or strict control over inline SVG output that this component abstraction does not expose.

How to Pitch It (Stakeholders)

For executives: This release makes the Tabler UX component library more flexible without forcing a redesign. Product teams can use multiple icon sets, including Lucide and MDI, while keeping a consistent Tabler-based UI. It is an additive, opt-in capability with no breaking changes, reducing vendor lock-in and avoiding custom icon-layer work.

For engineering: v0.8.0 adds prefixed Symfony UX Icons support to Icon and all icon props, rendering inline <svg> with existing variant, size, and animation classes. Unprefixed names still use the Tabler webfont, so migration can be gradual. Prefixed icons require symfony/ux-icons, now suggested. The Symfony UX Toolkit kit now pins @tabler/icons-webfont to 3.36.1+ for filled icons; verify that asset version during upgrade.

For product/design: We can standardize on one icon API while supporting multiple icon sets and a phased move from webfont to inline SVG. This enables faster UI iteration, better design-system alignment, and less custom component work.