-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Maximum call stack size exceeded #56614
Comments
Thanks, I believe this was a regression that slipped in in https://github.com/vercel/next.js/releases/tag/v13.5.4-canary.9 via #56281 We will have a look! |
I think it's an issue related to Also, see the open issue #468 |
I managed to work around the issue by reverting to an older version: |
I think this can be a same issue as #56550 |
This is the same issue as |
Hello, |
I've faced same issue with Nextjs 13.5.4.
|
### What? Update SWC crates, to apply bugfixes. ### Why? We adjusted the mangling option to make it identical with `swcMinify: false` with #56281, and it revealed some bugs of the name mangler of the SWC minifier. ### How? - Fixes #56550 - Fixes #56614 - Turbopack counterpart: vercel/turborepo#6171 ### Other Turbopack Changes * vercel/turborepo#6177 <!-- Tim Neutkens - Add support for FreeVarReference::Error --> * vercel/turborepo#6180 <!-- Tobias Koppers - fix chunk loading in build runtime --> * vercel/turborepo#6191 <!-- Justin Ridgewell - Deduplicate referenced_output_assets --> * vercel/turborepo#6171 <!-- Donny/강동윤 - build: Update `swc_core` to `v0.86.1` --> Closes WEB-1775 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
I'm still experiencing this issue with v13.5.6-canary.2 of next 🤔 |
@kelihansen If so, please file another issue. It's a different one. |
When using Material Tailwind, downgrading the next version to 13.5.3 solves the problem. 13.5.4 or higher will cause an error. v13.5.7-canary.9 as well. |
Thank you @NPJigaK, my issue was not during build, instead it was the same error at runtime in the browser console. Downgrade to 13.5.3 solved it. I couldn't even use a component that consisted of nothing but <Card>Hi</Card> without this happening. All of this worked perfectly in local run dev and I could always build fine, never once in 4 hours of debugging did it fail to build (except for typos), only deployment revealed the issue and only during runtime. That had me dissecting the chunk arrays in the build output, aka hell. |
@NPJigaK Does it happen with v13.5.7-canary.16? |
v13.5.7-canary.16 appears to fix the issue for me 🙌 |
@kdy1 It was fixed in v13.5.7-canary.16! Thanks! |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/Deeds67/nextjs-max-call-stack-size-exceeded
To Reproduce
"@material-tailwind/react": "^2.1.0",
NavbarDefault
component as listed here: https://www.material-tailwind.com/docs/react/navbar#navbarnpm run build
Current vs. Expected behavior
Current behavior:
Build fails with the following error:
RangeError: Maximum call stack size exceeded
Expected behavior: Build should successfully pass.
Here's the full error output:
Verify canary release
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #202309191142~1695998943~22.04~070916d SMP PREEMPT_DYNAMIC Fri S Binaries: Node: 20.3.1 npm: 9.6.7 Yarn: N/A pnpm: N/A Relevant Packages: next: 13.5.5-canary.4 eslint-config-next: 13.5.4 react: 18.2.0 react-dom: 18.2.0 typescript: 5.2.2 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Not sure
Additional context
App works when running
npm run dev
, but not when building a production ready app usingnpm run build
WEB-1744
The text was updated successfully, but these errors were encountered: