- How do I install ryangjchandler/blade-tabler-icons in a Laravel app?
- Install it with a single Composer require for ryangjchandler/blade-tabler-icons. Icon discovery is automatic through the blade-ui-kit/blade-icons manifest, so no config publishing is required for basic use. You need PHP 8.x and a Laravel version contemporary with the March 2024 release. A first working icon should take under 30 minutes in a skeleton app.
- Does blade-tabler-icons work with Laravel 11 or the latest Laravel version?
- The package was released around March 2024 and is archived, so it has not been tested against framework majors released afterward. Composer may still resolve it against current Laravel, but there will be no compatibility fixes if something breaks. Pin the exact version, commit your lockfile, and test any Laravel or PHP upgrade before relying on it in production.
- How do I render a Tabler icon in a Blade view?
- The package exposes Tabler icons as Blade components through blade-ui-kit/blade-icons, so you render an icon with a component such as x-tabler-home. It is a thin adapter rather than a custom rendering engine. Use the component in your Blade templates and customize SVG attributes through normal component usage.
- Do I need blade-ui-kit/blade-icons to use this package?
- Yes, blade-ui-kit/blade-icons is the real rendering dependency. This package registers the Tabler SVG icon set with blade-icons and exposes it to Blade. The fragile layer is the frozen icon-set registration, while blade-icons itself is actively maintained. If you already use blade-icons for another icon set, adoption is straightforward.
- Can I use blade-tabler-icons alongside Heroicons or Font Awesome?
- Yes, blade-ui-kit/blade-icons supports multiple icon sets, so Tabler icons can coexist with Heroicons, Font Awesome, or other registered sets. Adoption does not force a wholesale icon migration. You can introduce Tabler icons incrementally where they fit your design.
- Is ryangjchandler/blade-tabler-icons maintained or archived?
- The package is archived, meaning there are no security patches, no compatibility fixes for future PHP or Laravel majors, no new Tabler icons, and no responses to issues. Over a 12 to 24 month horizon it moves from low risk to a known-stale dependency. Dependency-hygiene tools such as composer audit will likely flag it, so expect to document an exception if you keep it.
- Does the package include all current Tabler icons?
- No. The package vendors a snapshot of the Tabler SVG set frozen around March 2024, so icons added upstream after that point will not be available. Designs referencing newer Tabler glyphs will silently fail unless you add SVGs yourself. Check your required icon inventory against the shipped set before committing to it.
- How do I cache or customize Tabler icons in Blade?
- The package is a thin adapter, so customization happens through Blade component usage and the underlying blade-icons integration rather than a large package-specific config surface. Optional caching and SVG attribute customization are available through blade-icons and your own wrapper component. Abstract usage behind a project-owned component so you can change the icon source later.
- How should I mitigate the archived-package risk in production?
- Pin the exact version, commit the lockfile, and wrap icon usage behind a project-owned component such as x-app.icon so call sites do not depend directly on Tabler. Document the archived status and assign an owner for eventual replacement. Track your Laravel and PHP upgrade cadence and test early, because the package will not receive compatibility fixes.
- What are the alternatives to blade-tabler-icons for Laravel Blade icons?
- If Tabler's visual language is not a hard requirement, choose an actively maintained set such as Heroicons, Lucide, or Phosphor through blade-icons. If Tabler is required, look for a maintained fork or successor package and check whether it ships icons added after March 2024. For SPA or Inertia front ends, consuming Tabler icons directly from npm is usually a better fit than a Blade-only adapter.