Admin panel unreachable after ^3.27.0 due to import map generation failure with: RangeError: Maximum call stack size exceeded
#11813
Comments
8times4
added
status: needs-triage
github-actions
bot
removed
the
validate-reproduction
|
Please add a reproduction in order for us to be able to investigate. Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided. Why was this issue marked with the
|
8times4
changed the title
RangeError: Maximum call stack size exceeded
|
The error you're encountering is related to the
One thing I noticed from what you shared is that you're mixing both "latest" and a specific version string: So I wonder if there's something old hanging around in your installation. I'd update your If the error relating to S3 persists, update your Hope this helps! |
DanRibbens
added
the
status: needs-repro
github-actions
bot
removed
the
status: needs-triage
|
After you've verified that you're using all the same versions of Payload, I would create a minimum reproduction that can be used to troubleshoot and identify the issue. You may have circular function calls in your code guessing from the error. |
|
I'm seeing a similar issue using version 3.31.0 after upgrading from 3.17.1. I tried running |
|
Thanks @BlainMaguire / @DanRibbens, that was really just cosmetic, I've always been on the same version across all payload packages, but since then I've been forcing versions. Will try to get a repro out within the next few days. |
|
I had the same issue as @edtorba in my project updated to payload 3.31.0. The problem was in the way the vercelBlobStorage plugin was conditionally initialized in the payload config file. Once I removed the condition that appends the plugin to the plugins array and used the enabled prop instead, the importMap was actually changed after running @@ -127,16 +127,15 @@ export default buildConfig({
globals: [Header, Footer, Settings],
plugins: [
...plugins,
- ...(process.env.BLOB_READ_WRITE_TOKEN
- ? [
+ ...[
vercelBlobStorage({
+ enabled: !!process.env.BLOB_READ_WRITE_TOKEN,
collections: {
[Media.slug]: true,
},
token: process.env.BLOB_READ_WRITE_TOKEN || '',
}),
- ]
- : []),
+ ],
],I believe it's the same configuration issue as with S3 storage plugin, see #11438 |
|
@tomasbarej legend, that fixed my problem |
|
Hey, I have similar problem to @edtorba had, but I don't use any plugins conditionally. After updating to v3.31.0 i can't generate importmap and types. I've tried to update on 2 different projects and both had the same issue, no idea what is causing this. |
|
I'm also having a ton of issues with this, freshly generated project. Anyone know the last stable version because this seems to have been a problem for a while? Or just anything that would get me unstuck to just go to production? Everything was fine until I added s3storage then everything went to heck. S3 config Runtime error payload generate:importmap output I cannot stress this enough, I have made zero changes to the generated codebase outside of adding the s3storage package and adding this plugin config. |
|
same problem but without any plugins |
|
@nicolasdabreo until it's fixed, you can use |
Describe the Bug
After upgrading to 3.27.0 (and now to 3.29.0) from 3.20.0, i'm no longer able to reach the
adminpanel in dev/prod.Based on my testing,
3.26.0is the last version that works, -3.27.0onwards introduces the call stack size error.Doesn't work with either pnpm or bun ( used to work with bun)
Following files use lexical:
Blocks:
Collections:
Fields:
src/heros/index.ts
tried cleaning the repo and reinstalling everything as well.
package.json:
payload.config.ts, with lexical part
I have
collectionsandblocksimporting lexical as well.i.e
Media.tsincollectionsThe text was updated successfully, but these errors were encountered: