Open reynaldichernando opened 2 hours ago
The reason this happens is that, there are 2 favicon.ico files in the landing page.
apps/web/app/favicon.ico
apps/web/public/favicon.ico
And seems like in production next.js, it is prioritizing the one in the app
directory.
However, in development, it will show the conflicting file error.
The fix should be fairly straightforward, simply by removing the default favicon.ico from the app
directory, so it uses the correct favicon from the public
directory. Will submit a PR for this!
Description
The favicon for the cap.so website is using the default vercel/next.js triangle icon.
https://cap.so/favicon.ico
Reproduction
or, open cap.so landing page
If opened in Safari, it will show the triangle icon.
If opened in Chrome, it will show the correct icon.
However, this is because Chrome is fetching the https://cap.so/favicon-32x32.png icon version.
Additional Context