37-5b82c79181d94cdf.js:1 Uncaught (in promise) TypeError: number 0 is not iterable (cannot read property Symbol(Symbol.iterator))

[tohsaka888]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Binaries:
Node: 16.17.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 12.3.1
eslint-config-next: 12.3.1
react: 18.2.0
react-dom: 18.2.0

What browser are you using? (if relevant)

chrome 105.0.5195.127

How are you deploying your application? (if relevant)

next start,vercel, netlify

Describe the Bug

When i use next start or use vercel/netlify to deploy my website,i got an error in console.

When i switch next.js to version 12.3.0,it does't have any error.

Expected Behavior

no error.

Link to reproduction

https://codesandbox.io/s/github/tohsaka888/coder-home

To Reproduce

first, build the application.

run next start.

see the console, it will have an error.

click, this button.

it will have another error.

repo

[balazsorban44]

From the looks of it, this might be an SWC minifier bug, but I cannot reproduce it currently, as the reproduction just produces CORS errors.

Could you try to create a more minimal reproduction of the issue? That would mean removing anything that is not directly contributing to the issue that you see. pages, APIs, packages, etc.

Can you try setting the swcMinfy: false option in your next.config.js to see if it makes a difference?

[tohsaka888]

From the looks of it, this might be an SWC minifier bug, but I cannot reproduce it currently, as the reproduction just produces CORS errors.

Could you try to create a more minimal reproduction of the issue? That would mean removing anything that is not directly contributing to the issue that you see. pages, APIs, packages, etc.

Can you try setting the swcMinfy: false option in your next.config.js to see if it makes a difference?

Thanks for your reply.When i switch swcMinify to false, the error is missing.

I think this error is acturally caused by SWC,should i close the issue?

[angelbeatsying]

when i upgrade to Next version 12.3.1, meet the same problem. when i use next/router jump to login page

[balazsorban44]

@tohsaka888 if it's an SWC bug, we still need to investigate to be able to fix the issue.

[balazsorban44]

@angelbeatsying could you link to your minimal reproduction? 🙏

[tohsaka888]

@balazsorban44 Maybe the version 12.3.1 of next.js is conflict with antd Menu component.When i remove the Menu of antd,the error is missing.By the way,the error is just occured in production mode.

[balazsorban44]

The error occurring only in production (deployed or next build && next start) means that it's a minifier bug since we don't minify in development (next dev).

Thanks for trying to narrow the problem down. Minimizing the reproduction repository is important for us to be able to identify the bug. If you have time to do so, please try removing any unnecessary code (pages, components, API, etc.) that does not contribute to the issue and post a simplified reproduction. 🙏 I tried yesterday, but your repository gave different errors than before, likely because you have pushed some new commits to it.

[tohsaka888]

@balazsorban44 I create a new repo to reproduce the error.Just use antd Menu component then i build this project and start it,you will see the error in console.

[balazsorban44]

Thanks! I could now confirm that the issue is fixed on the latest canary release! You can test it by running npm i next@canary, or wait for the fix to appear in the latest release.

[tohsaka888]

Thanks! I could now confirm that the issue is fixed on the latest canary release! You can test it by running npm i next@canary, or wait for the fix to appear in the latest release.

Thanks for your help!

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.