Vercel vs Heroku

[champsupertramp]

Has anyone successfully deployed more than 1,000 MDX files in Vercel? I'm planning on moving to Heroku as Vercel couldn't deploy the basic set up.

[shuding]

Hi! Would you mind sharing the error you had?

[champsupertramp]

Hi @shuding

The issue is the same with Heroku in free plan. I'm planning to upgrade the plan and see if it resolves the issue.

Here's the error from the Vercel:

21:12:56.403 | info  - Linting and checking validity of types...
21:12:56.629 | info  - Creating an optimized production build...
21:15:30.424 | Error: Command "npm run build" exited with SIGKILL

Here's the error from the Heroku:

info  - Linting and checking validity of types...
       info  - Creating an optimized production build...
[nextra] Init git repository failed Error: Discover git repo from [/tmp/build_83df3247] failed: could not find repository from '/tmp/build_83df3247'; class=Repository (6); code=NotFound (-3)
    at file:///tmp/build_83df3247/node_modules/nextra/dist/loader.mjs:248:37
    at Generator.next (<anonymous>)
    at fulfilled (file:///tmp/build_83df3247/node_modules/nextra/dist/chunk-HIDP27A7.mjs:36:24) {
  code: 'GenericFailure'
}
<--- Last few GCs --->
[1089:0x5b0fd60]   147755 ms: Mark-sweep (reduce) 2555.7 (2596.9) -> 2555.7 (2596.9) MB, 1968.0 / 0.0 ms  (average mu = 0.074, current mu = 0.003) allocation failure GC in old space requested
[1089:0x5b0fd60]   149771 ms: Mark-sweep (reduce) 2556.7 (2596.9) -> 2555.7 (2596.9) MB, 1994.1 / 0.0 ms  (average mu = 0.043, current mu = 0.011) allocation failure scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb06730 node::Abort() [node]
 2: 0xa1b6d0  [node]
 3: 0xce1dd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xce2177 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xe997e5  [node]
 6: 0xe9a2c6  [node]
 7: 0xea87ee  [node]
 8: 0xea9230 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xeac1ae v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xe6d6ea v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x11e6456 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x15da0d9  [node]
Aborted

[shuding]

I think it's not a platform issue then, maybe there's a memory leak in the Nextra code.

[champsupertramp]

Hi @shuding I'm checking where this memory leak is coming. By the way, most of the MDX files I've added recently has this template:
https://github.com/ultimatemember/docs-v3/blob/main/pages/developer/modules/groups/hooks/action/pre_groups_shortcode_query_list.mdx

[jeffreys-cat]

I have the same problem