You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that in version 9.5.4 next/head is treating the result from the nested component as a string, a tag name.
Screenshots
System information
Version of Next.js: 9.5.4
Version of Node.js: 10.15.0
Temporary solution
This can be fixed by updating the nested Favicons component to return a component like a similar PageMeta component does, and then un-nest it from the inside AppHead.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 29, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
It appears that in version
9.5.4
next/head is treating the result from the nested component as a string, a tag name.Screenshots
System information
Temporary solution
This can be fixed by updating the nested Favicons component to return a component like a similar PageMeta component does, and then un-nest it from the inside AppHead.
The text was updated successfully, but these errors were encountered: