Rspack: Maximum call stacksize exceeded
Hi, I'm trying to test out the
rspack
building in one of my project and I get this almost immediately when trying to do a build:
any idea what could go wrong with the rspack builder?
4 Replies
Hi @Ryan The Temp. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I don't have specific information about the Rspack builder or the exact error you're encountering. However, the error message you're seeing ("Maximum call stack size exceeded") is often related to recursive function calls or deep object structures that cause the JavaScript engine to exceed its call stack limit.
In Nuxt projects, this type of error can sometimes occur due to circular dependencies or overly complex configurations. Here are a few general suggestions that might help:
1. Check your project's dependencies for any circular references.
2. Review your Nuxt configuration files, especially
nuxt.config.js
, for any overly complex or deeply nested structures.
3. Ensure that all your Nuxt modules and plugins are compatible with your current Nuxt version.
4. Try updating your Nuxt and other dependencies to their latest compatible versions.
If the problem persists after trying these steps, you might want to create a minimal reproduction of the issue and report it to the Nuxt GitHub repository. The Nuxt team or community might be able to provide more specific guidance for your case.
For more information on troubleshooting Nuxt build issues, you can refer to the Nuxt documentation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@235835603458064394> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Weird. Looks like cyclic dependencies / references?
I'm not exactly sure, as build works fine without
rspack
.
you're saying circular dependencies in cjs?
I don't know if it makes any difference that I'm kicking off the build with bun
?
bun run build
is what i'm doing