Weave Code
Blade Memory Icons Laravel Package
codeat3/blade-memory-icons
A Laravel Blade package that provides simple Blade components for rendering Memory Icons in your views. Install via Composer, then use the included component syntax to add scalable SVG icons to your app with minimal setup.
A package to easily make use of "Memory Icons" in your Laravel Blade views.
Frequently asked questions about Blade Memory Icons
- How do I install codeat3/blade-memory-icons in a Laravel app?
- Install it with Composer by requiring codeat3/blade-memory-icons in your project. The package ships a Laravel service provider that is auto-discovered, so there is no manual registration step and no configuration file to publish. Once installed, the icon components are available in any Blade template.
- What Blade syntax do I use to render a Memory icon?
- Icons are rendered as Blade components using the x-memory-icon-* prefix, for example a self-closing component tag naming the specific icon. The exact prefix and the available icon names should be checked against the package README rather than assumed. No PHP imports or helper calls are needed inside your templates.
- Can I add CSS classes or change the size of a Memory icon?
- Yes. The components accept custom CSS classes and arbitrary HTML attributes, which is how you control sizing, color, and spacing with your own utility classes. Because the output is inline SVG, standard CSS like width, height, and currentColor applies directly. Attributes you pass through are rendered onto the SVG element.
- Which Laravel versions does codeat3/blade-memory-icons support?
- The package declares broad illuminate/* constraints, and release 1.2.0 widened them specifically to admit Laravel 13. That is a forward-compatibility widening rather than a behavioral change, so it means installation is permitted, not that the framework major is exercised in CI. Confirm the declared constraints and test against your exact Laravel version before pinning in production.
- Does this package need an icon font, npm build step, or CDN?
- No. Icons are output as inline SVG, so there is no icon font, no JavaScript runtime, no asset compilation, and no CDN in the request path. Installation is a single Composer require followed by component usage in your templates. That also means nothing extra to configure in your Vite or Mix pipeline.
- Is there any configuration or icon caching I can publish?
- The package itself adds no routes, migrations, or configuration surface; rendering and caching primitives come from its dependency on blade-ui-kit/blade-icons. If you need to tune icon caching or a component prefix, that is handled through the underlying blade-icons configuration. Check the README for whether this package exposes any prefix or cache options of its own.
- Does codeat3/blade-memory-icons work with Livewire or an Inertia frontend?
- It fits cleanly anywhere you render Blade server-side, including Livewire components and conventional Laravel monoliths. It is dead weight in an API-only service, and in an Inertia, React, or Vue frontend that resolves icons client-side you would be adding a dependency without gaining a capability. Match it to your rendering model before adopting it.
- How do I test that the Memory icon components render correctly?
- Because the output is plain inline SVG in Blade, you can assert on rendered markup with the usual response assertions in your feature tests. Render a view containing an icon component and assert the expected SVG markup or class attribute appears. Keeping a small smoke test per icon you actually ship also guards against component names changing on upgrade.
- Will inline SVG icons bloat my HTML and hurt performance?
- Each component inlines full SVG markup, which increases HTML size on icon-dense pages and prevents reuse of a shared sprite. For a handful of icons this is negligible, but for long lists or tables it is a page-weight and performance-budget concern. Accessibility is also left to your template, so decide deliberately between decorative aria-hidden output and labeled icons.
- What license covers the Memory Icons SVG set, and how does this compare with alternatives?
- The package code is MIT, but it redistributes a third-party SVG icon set whose terms must be confirmed separately, and compiled inline markup may carry attribution obligations worth recording in a notices file. Functionally it is a thin wrapper over blade-ui-kit/blade-icons, so alternatives like Heroicons or a sibling icon pack offer the same component model. Note that this repo is single-maintainer with zero stars and zero dependents, so support latency across the maintainer's icon packages is correlated and the due diligence has to come from your team.
Weaver
How can I help you explore Laravel packages today?