Skip to content
Discussion options

You must be logged in to vote

So @leerob, after a LOT of digging down, It turned out this was happening because the favicons were placed in a nested folder public/favicons and moving them to the root resolved the issue completely.

If this is not a normal behavior of Next.js and it should be reported as a bug, please let me know and I will create an issue and supply a Codesandbox replicating the issue!

furthermore, thank you very much for taking the time to answer my question.

Cheers!

Replies: 3 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@leerob
Comment options

@ghost
Comment options

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
1 participant