System crashed while using the content-based file convention with maximum heap memory usage

[jeevankc17]

Describe the bug Hey this is my current project structure

I have contentDirBasePath: "/license" on the next.config.ts file for now

Now I tried to put all the existing 3 folder from the app directory into the content directory, as I want them as a separate page, I tried to make contentDirBasePath: "/ " on next.config.ts and give href accordingly on _meta.json.

Suddenly got issue like maximum resource used in heap memory of the nodejs and everything crashed.

I think that might be lot of static files been built or there was limitation around the content-based file system mapping multiple directories at once. I don't have any clue

Is there any limitation using the content-based directory then using page.mdx file?
Is content based file convention is really a bottleneck?
Nextra team doesnot mention that downside on their documentation.
Do I need to focus on page.mdx approach?

[dimaMachina]

please create a reproduction repo

[jeevankc17]

Hey @dimaMachina Nextra by default build every mdx file statically at build times since I have more than 400 mdx files and I can't build all that on a vercel free plan , anyways I mean this consuming lots of memory.
I am planning to implement dynamic import like this

Is this the way.
please mention any articles regarding this if there I did not find any

[jeevankc17]

@dimaMachina

Same issue on local environment too taking lots of memory to build and still exhausted as every file being built statically at once,
How to solve this?

[jeevankc17]

@dimaMachina hey ?

[dimaMachina]

#4098 (comment)