- How do I install jeffersongoncalves/laravel-favicon?
- Install it with Composer by requiring jeffersongoncalves/laravel-favicon in your Laravel application. Laravel package discovery registers the service provider automatically, and you can publish the package configuration if you need to customize icon paths or routes.
- How does the package serve favicon.ico and browserconfig.xml?
- The package registers routes that respond with favicon.ico and browserconfig.xml based on your package configuration. The referenced icon assets are resolved through Vite, so the routes and generated head links stay aligned with your built assets.
- How do I add the favicon links to a Blade layout?
- Use the package's Blade helper in the head section of your layout to output the Apple touch icon, PNG icon, and related link tags. The helper reads your configured, Vite-resolved assets so you do not need to hard-code asset URLs in every layout.
- Can I customize the favicon assets and routes through config?
- Yes. The package is config-driven, so you can publish the config and point it at your preferred favicon, browserconfig, Apple touch icon, and PNG assets. Route and asset behavior should be adjusted through that configuration rather than editing package source.
- Does it support Apple touch icons and PNG icons, not just favicon.ico?
- The package is designed to serve favicon.ico and browserconfig.xml routes and to add Apple touch icon and PNG touch icon head links. That helps cover desktop browsers, iOS home screen icons, and other device-specific icon needs.
- How does Vite asset resolution work with Laravel favicons?
- The package resolves configured icon assets through Vite, so references can follow your Vite build output instead of hard-coded public paths. After building assets, verify the generated favicon and touch icon URLs in your rendered HTML.
- Which Laravel versions does jeffersongoncalves/laravel-favicon support?
- The exact Laravel and PHP version constraints are defined in the package's composer.json. Check those requirements before installing, especially if your application is on an older Laravel release.
- Do I need to generate a full favicon set before using this package?
- The package includes helpers intended to help create favicon sets, but you can also provide your own configured icon files. At minimum, make sure the favicon.ico, browserconfig.xml, and any Apple or PNG assets referenced in config exist and resolve correctly.
- Is this package safe to use in production?
- It is a standard Laravel package that serves configured icon routes and renders head links, so it can be used in production when your assets are built and configured correctly. Test the favicon.ico and browserconfig.xml routes plus the rendered Blade head links in your deployed environment.
- What are alternatives to using a Laravel favicon package?
- You can manually place icons in your public directory and add link tags directly in Blade, but you then manage routes and Vite paths yourself. Other Laravel favicon packages may offer different generators or config conventions; compare their Vite support and maintenance before switching.