-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
37-5b82c79181d94cdf.js:1 Uncaught (in promise) TypeError: number 0 is not iterable (cannot read property Symbol(Symbol.iterator)) #40889
Comments
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 |
Thanks for your reply.When i switch I think this error is acturally caused by SWC,should i close the issue? |
when i upgrade to Next version 12.3.1, meet the same problem. when i use next/router jump to login page |
@tohsaka888 if it's an SWC bug, we still need to investigate to be able to fix the issue. |
@angelbeatsying could you link to your minimal reproduction? 🙏 |
@balazsorban44 Maybe the version 12.3.1 of |
The error occurring only in production (deployed or 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. |
@balazsorban44 I create a new repo to reproduce the error.Just use antd Menu component then i |
Thanks! I could now confirm that the issue is fixed on the latest |
Thanks for your help! |
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. |
Verify 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 version12.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
The text was updated successfully, but these errors were encountered: