- How do I install poldixd/laravel-feather?
- Install it with Composer by running composer require poldixd/laravel-feather. Laravel's package discovery registers the service provider automatically, so no manual registration is required. Choose the package major that matches your Laravel major, since the version numbers track the framework. Once installed you can call the Blade component from any template.
- Does poldixd/laravel-feather support Laravel 13?
- Yes. Version 13.0.0 was released specifically to add Laravel 13 support, and the package's major version now tracks the Laravel major it targets. That means 13.x is intended for Laravel 13 applications, while earlier majors remain the correct choice for Laravel 11 and Laravel 12 estates. Check the composer.json constraints on Packagist to confirm the exact PHP and Laravel floors before upgrading.
- How do I use a Feather icon as a Blade component?
- Call the package's Blade component in any view and pass the Feather icon name as an attribute; the README shows the exact tag and attribute names. The component renders inline SVG at render time, so the icon inherits font color and sizing from the surrounding CSS. You can add classes and extra attributes directly on the tag to customize each instance.
- Can I use Feather Icons with a Blade include() instead of a component?
- The package is designed to work both as a Blade include() and as a Blade component, so you can pick whichever matches your template style. Includes are convenient in older codebases or when markup is generated programmatically, while the component gives cleaner attribute-driven customization. Both routes produce the same inline SVG output.
- How do I set default CSS classes and attributes for every icon?
- Publish the package config file and define your default classes and attributes there once instead of repeating them on every icon tag. Each component render then picks up those defaults, which keeps your Blade markup clean and consistent. You can still override or append classes per instance when a specific icon needs different styling.
- Do I need an icon font or JavaScript to use Feather Icons in Laravel?
- No. The package renders Feather Icons as inline SVG on the server, so there is no icon font to load, no JavaScript bundle, and no external sprite request. Inline SVG also means icons inherit currentColor and can be styled or animated with plain CSS. That keeps the page lighter than font-based or JS-driven icon solutions.
- How do I change the size, color, or stroke width of a Feather icon?
- Because the output is inline SVG, size and color typically come from CSS: set width, height, and color through the icon's classes. Stroke width and other SVG presentation attributes can be passed through as attributes on the component tag. Both approaches work alongside the package's default class configuration.
- Is poldixd/laravel-feather safe to use in production?
- It is a thin Blade wrapper that outputs static inline SVG, so runtime risk is minimal: no JavaScript, no external HTTP calls, and no database interaction. The real production concern is version alignment, so pin the package major that matches your Laravel major in composer.json. Read the release notes for each major, since these bumps are often used to drop support for end-of-life PHP and Laravel versions.
- What changed in version 13.0.0 and is it a breaking change?
- The 13.0.0 release adds Laravel 13 support and migrates the test suite from PHPUnit-style tests to Pest; no public API changes or deprecations were documented. The major bump mainly aligns the package with Laravel 13, but majors are also a common place to quietly drop end-of-life PHP and Laravel support. If you are staying on Laravel 11 or 12, keep using the matching earlier major and verify requirements before jumping.
- How do I upgrade poldixd/laravel-feather to 13.0.0?
- Raise the package constraint together with your PHP and Laravel constraints in a single Composer operation so the solver resolves them as one problem rather than three. Do it on a branch and run your application's test suite plus any publish steps the package documents. Diff any published config or asset files against what you currently have vendored, then merge through your normal release process.