Closed da-kicks-87 closed 1 week ago
The next-intl
examples currently simply put a favicon.ico
in public
—that seems to work for me. I'm not aware of if there are implications for other patterns. There might be details relevant to your app, like a potential matcher
you're using the middleware config.
I'll move this to a discussion since it's a Next.js usage question and not a bug report about next-intl
.
Description
This is for Next.js 14.2.16. - App Router
Hello after installing next-intel the favicon no longer load from the file-based metadata system. I had tried to have the favion.ico in
/src/app/[locale]
and/src/app
. (https://nextjs.org/docs/app/api-reference/file-conventions/metadata/app-icons)I got the favicons to work by doing the alternative by using Next.js metadata export object and putting the favicons in the
/public/favicons
Eg from layout.js:
However the Next.js guide mention i should be using the special metadata files inside the app folder for favicons. What should I do?
Verifications
Mandatory reproduction URL
/sorry-offline
Reproduction description
See above description
Expected behaviour
See above description