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 10][Next/Image] Image in Head breaks at build/server render time #18799

Closed
conanbatt opened this issue Nov 4, 2020 · 3 comments
Closed
Assignees
Milestone

Comments

@conanbatt
Copy link

conanbatt commented Nov 4, 2020

Bug report

Images under an tag breaks at build/server render time

To Reproduce

Repo: https://github.com/conanbatt/nextjs-webpack-5-images

  1. yarn build
    OR
  2. yarn dev -> go to /

Alternatively run this snippet in a page:

<Head>
  <noscript>
    <img src="" />
  </noscript>
</Head>

Expected behavior

Does not produce error

Screenshots

image

System information

  • Version of Next.js: [e.g. 10.0.1]
  • Version of Webpack: [e.g. 5.4.0]

Additional context

I believe this might be related to image changes in Next 10. The error points to the image tag being transformed into something that can't be processed. Does not happen on Next 9.5.3 and webpack 4

I was able to skirt around it by doing:

<noscript>
 {[<img src="" key="1]}
</noscript>
@conanbatt conanbatt added the bug Issue was opened via the bug report template. label Nov 4, 2020
@conanbatt conanbatt changed the title [Next 10][Next/Image] Image under noscript tags break at build/server render time [Next 10][Next/Image] Image in Head breaks at build/server render time Nov 4, 2020
@timneutkens
Copy link
Member

Looks like a duplicate of #17721

@Timer Timer added this to the iteration 13 milestone Nov 7, 2020
@Timer Timer added kind: bug and removed bug Issue was opened via the bug report template. labels Nov 7, 2020
@Timer Timer added the point: 2 label Nov 17, 2020
@timneutkens timneutkens modified the milestones: iteration 13, iteration 14 Dec 1, 2020
@Timer Timer self-assigned this Dec 31, 2020
@Timer
Copy link
Member

Timer commented Jan 4, 2021

This is no longer broken on canary.
image

@Timer Timer closed this as completed Jan 4, 2021
@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 28, 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

4 participants