- How do I install eduard9969/blade-polaris-icons?
- Install it with Composer by running composer require eduard9969/blade-polaris-icons. The package is a view-layer dependency, so it does not require migrations or database setup. After installation you can use the provided Blade components or directive in your views. Check the README for the exact component names and any optional publishing steps.
- Which Laravel versions does blade-polaris-icons support?
- Version 2.9.0 adds Laravel 13 support by widening the framework version constraint. Earlier 2.x releases target prior Laravel majors. Because the package tracks Laravel majors, confirm the resolved illuminate/support version matches your application constraint. If you are pinned below Laravel 13, the 2.9.0 change is effectively inert for you.
- How do I render a Polaris icon in a Laravel Blade view?
- The package exposes the Polaris icon set through Blade components, so you can drop an icon into a view with a concise tag instead of managing raw SVG files. You typically reference the icon by name and can pass attributes such as size or class depending on the component API. See the README for exact component names and supported attributes.
- Can I change the size, color, or CSS classes of the icons?
- Yes, the package is designed for clean, customizable SVG icons in Blade. You can usually control presentation with attributes like class, width, height, or inline styles passed to the component. For color, prefer currentColor or CSS so icons inherit your design system. Verify the specific props in the README because the component API defines what is passed through.
- Does blade-polaris-icons require a service provider or config file?
- It is a thin presentation-layer package. Any service provider exists only to register Blade components or an icon namespace, not to touch the container in meaningful ways. It does not publish migrations and generally does not require configuration. You can use it as a leaf dependency in any Blade-rendered Laravel app.
- Is blade-polaris-icons safe to use in production?
- The risk profile is low because it only renders SVG icons at the view layer with no persistence, queues, auth, or background processing. The main production concern is your asset build: if you purge CSS or compile Tailwind, make sure any classes used by the icons are safelisted so they are not tree-shaken. Run a production asset build and view-rendering tests before deploying.
- How do I upgrade blade-polaris-icons from 2.8.0 to 2.9.0?
- Bump the constraint to ^2.9 and run composer update eduard9969/blade-polaris-icons. The 2.9.0 release is a single change adding Laravel 13 support, with no new APIs, removals, or migration steps called out. Treat it as a constraint-widening patch and confirm your views still resolve. If you are upgrading Laravel at the same time, do both in the same branch.
- Will Tailwind purge or tree-shake the Polaris icon classes?
- Build tools only remove CSS classes they cannot detect in your source. If your icon component names or classes are generated dynamically, Tailwind's content scanner may miss them. Safelist the relevant classes or ensure the package's icon classes appear in scanned templates. Always validate with a production asset build, not just a dev server.
- What are alternatives to eduard9969/blade-polaris-icons?
- Alternatives include blade-ui-kit/blade-icons with an icon set, manually maintained SVG partials, or a broader icon package such as Heroicons or Font Awesome for Laravel. Choose Polaris icons only if your product uses a Shopify-adjacent design language; otherwise you are importing another system's iconography. A local Blade component shim is also possible if you want to avoid the dependency.
- Who maintains blade-polaris-icons, and what happens if it is abandoned?
- The package is maintained by Eduard9969 as a single-maintainer project. The prompt Laravel 13 support is a positive maintenance signal, but continuity is not guaranteed. Because icons are consumed through Blade component names, you can create a local shim that maps the same names to bundled SVGs if needed. Review the licensing terms for the bundled Polaris assets before redistributing them.