Weave Code
Laravel Favicon Generator Laravel Package
infernalmedia/laravel-favicon-generator
A small Laravel package that generates favicons from a source image via an Artisan command. It produces the common icon sizes and formats, stores them in your public directory, and gives you the HTML tags to drop into your Blade layouts.
Package to generate favicons within your Laravel application.
Frequently asked questions about Laravel Favicon Generator
- How do I install infernalmedia/laravel-favicon-generator?
- Install it with Composer using composer require infernalmedia/laravel-favicon-generator. The package registers itself through Laravel's package auto-discovery, so no manual service provider registration is needed on supported versions. After installing, publish the config file, drop your source image in place, and run the generation command. Because v2.0.0 is a major release, pin the version you have verified rather than floating blindly.
- Which Laravel and PHP versions does this favicon package support?
- The supplied release notes for v2.0.0 only link to a changelog, so the exact minimum PHP and Laravel versions are not confirmed in the documentation provided here. A major version bump commonly raises the PHP floor and the Laravel major supported, so verify the composer.json constraints before adopting. Check the changelog and the package's require block against your application's PHP and Laravel versions first. That compatibility check is the single blocking unknown for most teams.
- How do I generate favicons in Laravel from a single source image?
- Place your source image where the package config expects it, then run the provided Artisan command to generate the icon set. The package can also be triggered via a route, which is handy for one-off generation in a browser-driven workflow. Generation produces the common sizes and formats and writes them to your public directory. You then copy the supplied HTML tags into your Blade layout.
- What favicon sizes and formats does laravel-favicon-generator produce?
- It generates a standard favicon set: an ICO file, multiple PNG sizes, Apple touch icons, and web manifest entries. All assets are written into your public directory so they are served as static files. If you need obscure platform-specific sizes, check the config for the exact list before assuming coverage. The output is aimed at covering the everyday browser, iOS, and PWA cases rather than every legacy target.
- How do I add the generated favicons to my Blade layout?
- The package gives you the HTML link and meta tags to drop into your Blade layout's head section. Put them in your base layout or a dedicated partial so every page inherits them. Because the assets live in the public directory, the tags reference plain static paths and work fine alongside Vite or Mix. Keep the manifest link in the same partial to avoid drift.
- Where does the package store favicon files, and can I change the output location?
- Generated icons are stored in your public directory so they can be served directly without a controller. The exact paths and filenames are controlled by the published config file, which you should review after installing. If you relocate assets, update the HTML tags you copied into Blade to match. Note that v2.0.0 may have renamed config keys or output paths, so diff the published config against your usage when upgrading.
- What changed in v2.0.0 and how do I upgrade from v1?
- The provided release notes only contain a changelog URL, so the specific breaking surface is unconfirmed here: config schema, command signatures, namespaces, output paths, and the PHP/Laravel floor could all have moved. Treat compatibility as not assumed across a major boundary. If you already run v1, pin to ^1.0 until you have diffed the changelog against your usage, and avoid floating to ^2.0 on a shared branch. For greenfield installs, start on v2 after reviewing the changelog.
- Does the package require GD or Imagick, and what happens if neither is installed?
- Favicon generation depends on an image manipulation layer, typically GD or Imagick, so the relevant PHP extension must be available everywhere generation runs, including CI and container images. Whether v2 treats that backend as a hard or soft dependency is not confirmed in the supplied notes. If the extension is missing, failures tend to surface at runtime during generation rather than at install time. Add the extension to your Dockerfile and CI image to avoid silent surprises.
- Should I commit generated favicons to the repo or generate them at deploy time?
- Either works, but the choice affects your CI/CD pipeline. Committing the generated public assets keeps deploys simple and avoids needing GD or Imagick in production containers. Generating at deploy time keeps the source image as the single truth but requires the image extension in every environment where the command runs. Whichever you pick, make sure the HTML tags in Blade stay in sync with the actual output paths.
- Is infernalmedia/laravel-favicon-generator actively maintained, and what are the alternatives?
- It is a single-maintainer, low-activity package, and the v2.0.0 release ships changelog-only notes, which is a mild signal about release hygiene. The blast radius is low because it is asset-only: a failure means missing or stale favicons, not downtime. That argues for a time-boxed spike and a pinned version rather than a formal architecture review. Alternatives include standalone favicon generator services, realfavicongenerator output committed as static files, or rolling your own Artisan command with an image library you already depend on.
Weaver
How can I help you explore Laravel packages today?