Weave Code
Blade Teeny Icons Laravel Package
codeat3/blade-teeny-icons
codeat3/blade-teeny-icons is a Laravel Blade component package for easily embedding Teeny Icons SVG icons in your views. Use simple Blade tags, customize size and attributes, and keep icon markup clean and consistent.
A package to easily make use of "Teeny Icons" in your Laravel Blade views.
Frequently asked questions about Blade Teeny Icons
- How do I install codeat3/blade-teeny-icons in a Laravel application?
- Run composer require codeat3/blade-teeny-icons. The package's service provider is auto-discovered, so there is nothing to register in config/app.php and no artisan command to run. Once installed you can immediately use the components in any Blade view. No npm, Vite build step, or published assets are required.
- What Blade syntax do I use to render a Teeny Icon?
- Each icon is registered as an anonymous Blade component named after the icon, so you render it with a tag like <x-teeny-icon-name />. The kebab-case icon name maps to the component, and self-closing tags work fine. The component outputs inline SVG directly into your template, so no extra wrapper markup is needed.
- How do I change the size, color, or CSS class of a Teeny Icon in Blade?
- Pass standard HTML attributes to the component tag, such as class, width, height, fill, or stroke. Because the output is inline SVG you can style it with Tailwind or plain CSS using currentColor and text-size utilities. Attributes are applied to the underlying SVG element, which keeps styling consistent with the rest of your markup.
- Which Laravel and PHP versions does codeat3/blade-teeny-icons support?
- The package targets Laravel applications on PHP 8.x and follows the same conventions as the sibling blade-heroicons and blade-tabler-icons packages. Release 1.12.0 added Laravel 13 compatibility, but the changelog does not state whether the illuminate/support constraint was widened additively or rewritten. Check the composer.json constraint diff before adopting it if you are still on an older Laravel major, since a rewritten constraint could drop support for Laravel 9 through 11.
- Do I need npm, Vite, or to publish assets to use this package?
- No. The icons ship as inline SVG rendered by Blade components, so there is no asset pipeline, no node_modules dependency, and no vendor:publish step. Installation is a single Composer require and the service provider is auto-discovered. That also means there is no build step to rerun after upgrading the package.
- Can I use these icon components in Livewire, mailables, and PDF templates?
- Yes. The components are plain Blade, so they render anywhere Blade runs: Livewire and HTMX fragments, email templates, error pages, and PDF generation views. Because the output is inline SVG rather than an external image reference, it survives contexts where assets cannot be fetched, such as many mail clients and PDF renderers. Do verify that the SVG renders acceptably in older email clients before relying on it.
- Can I install codeat3/blade-teeny-icons alongside blade-heroicons or blade-tabler-icons?
- You can co-install several icon set packages, and they follow identical conventions so the Blade syntax stays consistent across sets. The risk is component name collisions: each package registers a large number of components at boot, and an overlapping icon name fails silently by rendering the wrong set. The teeny prefix on <x-teeny-icon-*> mitigates this, but review registered namespaces and boot overhead if you stack several sets.
- Is codeat3/blade-teeny-icons actively maintained?
- It is a community package with a single maintainer, no vendor backing, and effectively no ecosystem gravity, since low stars and no dependents mean few teams exercise it against new Laravel releases. The Laravel 13 compatibility bump was submitted by the author, which is a good engagement signal, but the compatibility claim ultimately rests on one person's workflow. Because the payload is static SVG, forking or vendoring is a cheap contingency, but assign that owner before adoption rather than after.
- How do I find the correct Teeny Icon component name?
- Component names are derived from the upstream Teeny Icons SVG file names, typically converted to kebab-case and prefixed, so finding the icon on the Teeny Icons site gives you the base name. You then render it as <x-teeny-icon-your-name />. Because upstream additions and renames propagate into component names, pin the package version if you need names to stay stable across deployments.
- Does the package sanitize SVG output, and what does that mean for CSP and page weight?
- The package assumes a trusted build-time SVG source rather than implementing a sanitization boundary, which is fine for a curated icon set but means you should not point it at user-supplied SVG. Output is emitted inline per usage and is not deduplicated, so icon-dense views carry a real payload cost. If you run a strict Content-Security-Policy, account for inline SVG in your policy and consider caching or partials for heavily repeated icons.
Weaver
How can I help you explore Laravel packages today?