Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next/head treating result from nested components as string tag in v9.5.4 #17884

Closed
evanderson opened this issue Oct 14, 2020 · 2 comments
Closed

Comments

@evanderson
Copy link

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

Screen Shot 2020-10-14 at 9 01 07 AM
Screen Shot 2020-10-14 at 9 01 18 AM

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.

@jamesmosier
Copy link
Contributor

Closing as a duplicate of #17721

@balazsorban44
Copy link
Member

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 vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants