nextjs - 💡(How to fix) Fix Next.js can't work with the mingw nodejs [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#90403Fetched 2026-04-08 00:20:14
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

Cannot execute it due to the same error. But the key enviroment should be mingw64.

Code Example

# npm run dev

> my-app@0.1.0 dev
> next dev


thread '<unnamed>' (18296) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread '<unnamed>' (18296) panicked at library\core\src\panicking.rs:230:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fffebe937b2 - napi_register_module_v1
   1:     0x7fffebe9b98a - napi_register_module_v1
   2:     0x7fffebe6b617 - napi_register_module_v1
   3:     0x7fffebe7ec65 - napi_register_module_v1
   4:     0x7fffebe85149 - napi_register_module_v1
   5:     0x7fffebe84f38 - napi_register_module_v1
   6:     0x7fffebe85a0a - napi_register_module_v1
   7:     0x7fffebe85762 - napi_register_module_v1
   8:     0x7fffebe7ee6f - napi_register_module_v1
   9:     0x7fffebe6738e - napi_register_module_v1
  10:     0x7fffee4a33a5 - wasmer_vm_throw
  11:     0x7fffee4a32f3 - wasmer_vm_throw
  12:     0x7fffee4a3521 - wasmer_vm_throw
  13:     0x7fffee49d2c3 - wasmer_vm_throw
  14:     0x7fffee4028d0 - napi_register_module_v1
  15:     0x7fffee3f9284 - napi_register_module_v1
  16:     0x7ff8b46b1d86 - RtlCaptureContext2
  17:     0x7fffee49d2a7 - wasmer_vm_throw
  18:     0x7fffe929d05d - <unknown>
  19:     0x7fffebe055a4 - napi_register_module_v1
  20:     0x7fffebdfa759 - napi_register_module_v1
  21:     0x7ff816889098 - napi_create_threadsafe_function
  22:     0x7ff81688cb0e - node_module_register
  23:     0x7ff816827f67 - ZN4node17SetCppgcReferenceEPN2v87IsolateENS0_5LocalINS0_6ObjectEEEPv
  24:     0x7ff81688b6f8 - node_module_register
  25:      0x1cc1fdcf64d - <unknown>
  26:      0x1cc1fdcdbd4 - <unknown>
  27:      0x1cc00056fdd - <unknown>
  28:      0x1cc000953ed - <unknown>
  29:      0x1cc00140465 - <unknown>
  30:      0x1cc00093de1 - <unknown>
  31:      0x1cc0009416f - <unknown>
  32:      0x1cc0005447b - <unknown>
  33:      0x1cc0009430f - <unknown>
  34:      0x1cc1fdcdbd4 - <unknown>
  35:      0x1cc1fdcdbd4 - <unknown>
  36:      0x1cc1fef93fd - <unknown>
  37:      0x1cc1fdce4ba - <unknown>
  38:      0x1cc1ff82d81 - <unknown>
  39:      0x1cc1fdcdbd4 - <unknown>
  40:      0x1cc1fdcdbd4 - <unknown>
  41:      0x1cc1fe1113b - <unknown>
  42:      0x1cc1fefae75 - <unknown>
  43:      0x1cc1fdfed47 - <unknown>
  44:      0x1cc1fdcb67b - <unknown>
  45:     0x7ff81708d83e - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  46:     0x7ff81708e7fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  47:     0x7ff81708e8fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  48:     0x7ff8170c43b8 - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  49:     0x7ff8170c47cb - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  50:     0x7ff8167d2aaf - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  51:     0x7ff8167d2d7d - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  52:     0x7ff8168dae78 - ZN4node12OnFatalErrorEPKcS1_
  53:     0x7ff8168e0d21 - ZN4node12OnFatalErrorEPKcS1_
  54:     0x7ff81960e750 - ZN2v84base4bits21RoundUpToPowerOfTwo64Ey
  55:     0x7ff816bd0fa5 - uv_barrier_destroy
  56:     0x7ff816bd5801 - uv_async_send
  57:     0x7ff816bd661f - uv_run
  58:     0x7ff8167d5ee3 - ZN4node22CommonEnvironmentSetup21CreateForSnapshottingEPNS_20MultiIsolate
PlatformEPSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS9_EERKSB_SE_RKNS_14Snaps
hotConfigE
  59:     0x7ff81692dc17 - ZN4node12OnFatalErrorEPKcS1_
  60:     0x7ff81692e21f - ZN4node12OnFatalErrorEPKcS1_
  61:     0x7ff816881ed1 - ZN4node5StartEiPPc
  62:     0x7ff6195b1576 - <unknown>
  63:     0x7ff6195b10c9 - <unknown>
  64:     0x7ff6195b1416 - <unknown>
  65:     0x7ff8b4247374 - BaseThreadInitThunk
  66:     0x7ff8b465cc91 - RtlUserThreadStart
thread caused non-unwinding panic. aborting.

thread '<unnamed>' (13632) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread '<unnamed>' (13632) panicked at library\core\src\panicking.rs:230:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fffebe937b2 - napi_register_module_v1
   1:     0x7fffebe9b98a - napi_register_module_v1
   2:     0x7fffebe6b617 - napi_register_module_v1
   3:     0x7fffebe7ec65 - napi_register_module_v1
   4:     0x7fffebe85149 - napi_register_module_v1
   5:     0x7fffebe84f38 - napi_register_module_v1
   6:     0x7fffebe85a0a - napi_register_module_v1
   7:     0x7fffebe85762 - napi_register_module_v1
   8:     0x7fffebe7ee6f - napi_register_module_v1
   9:     0x7fffebe6738e - napi_register_module_v1
  10:     0x7fffee4a33a5 - wasmer_vm_throw
  11:     0x7fffee4a32f3 - wasmer_vm_throw
  12:     0x7fffee4a3521 - wasmer_vm_throw
  13:     0x7fffee49d2c3 - wasmer_vm_throw
  14:     0x7fffee4028d0 - napi_register_module_v1
  15:     0x7fffee3f9284 - napi_register_module_v1
  16:     0x7ff8b46b1d86 - RtlCaptureContext2
  17:     0x7fffee49d2a7 - wasmer_vm_throw
  18:     0x7fffe929d05d - <unknown>
  19:     0x7fffebe055a4 - napi_register_module_v1
  20:     0x7fffebdfa759 - napi_register_module_v1
  21:     0x7ff816889098 - napi_create_threadsafe_function
  22:     0x7ff81688cb0e - node_module_register
  23:     0x7ff816827f67 - ZN4node17SetCppgcReferenceEPN2v87IsolateENS0_5LocalINS0_6ObjectEEEPv
  24:     0x7ff81688b6f8 - node_module_register
  25:      0x2579fdcf64d - <unknown>
  26:      0x2579fdcdbd4 - <unknown>
  27:      0x25780097d9d - <unknown>
  28:      0x25780091f6d - <unknown>
  29:      0x2578011aae5 - <unknown>
  30:      0x25780123603 - <unknown>
  31:      0x257801169e1 - <unknown>
  32:      0x25780122ea5 - <unknown>
  33:      0x2579fdcdbd4 - <unknown>
  34:      0x2579fdcdbd4 - <unknown>
  35:      0x2579fef93fd - <unknown>
  36:      0x2579fdce4ba - <unknown>
  37:      0x2579ff82d81 - <unknown>
  38:      0x2579fdcdbd4 - <unknown>
  39:      0x2579fdcdbd4 - <unknown>
  40:      0x2579fe1113b - <unknown>
  41:      0x2579fefae75 - <unknown>
  42:      0x2579fdfed47 - <unknown>
  43:      0x2579fdcb67b - <unknown>
  44:     0x7ff81708d83e - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  45:     0x7ff81708e7fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  46:     0x7ff81708e8fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  47:     0x7ff8170c43b8 - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  48:     0x7ff8170c47cb - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  49:     0x7ff8167d2aaf - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  50:     0x7ff8167d2d7d - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  51:     0x7ff8168dae78 - ZN4node12OnFatalErrorEPKcS1_
  52:     0x7ff8168e0d21 - ZN4node12OnFatalErrorEPKcS1_
  53:     0x7ff81960e750 - ZN2v84base4bits21RoundUpToPowerOfTwo64Ey
  54:     0x7ff816bd0fa5 - uv_barrier_destroy
  55:     0x7ff816bd5801 - uv_async_send
  56:     0x7ff816bd661f - uv_run
  57:     0x7ff8167d5ee3 - ZN4node22CommonEnvironmentSetup21CreateForSnapshottingEPNS_20MultiIsolate
PlatformEPSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS9_EERKSB_SE_RKNS_14Snaps
hotConfigE
  58:     0x7ff81692dc17 - ZN4node12OnFatalErrorEPKcS1_
  59:     0x7ff81692e21f - ZN4node12OnFatalErrorEPKcS1_
  60:     0x7ff816881ed1 - ZN4node5StartEiPPc
  61:     0x7ff6195b1576 - <unknown>
  62:     0x7ff6195b10c9 - <unknown>
  63:     0x7ff6195b1416 - <unknown>
  64:     0x7ff8b4247374 - BaseThreadInitThunk
  65:     0x7ff8b465cc91 - RtlUserThreadStart
thread caused non-unwinding panic. aborting.

---

# npx next info

thread '<unnamed>' (20708) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded

Cannot execute it due to the same error. But the key enviroment should be mingw64.
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

NA (this is not necessary with the issue)

To Reproduce

make sure you're in mingw enironment.

use npx create-next-app to create a default app, and run npm run dev.

Current vs. Expected behavior

Expect app successfully to start up, currently the following errors occured,

# npm run dev

> [email protected] dev
> next dev


thread '<unnamed>' (18296) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread '<unnamed>' (18296) panicked at library\core\src\panicking.rs:230:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fffebe937b2 - napi_register_module_v1
   1:     0x7fffebe9b98a - napi_register_module_v1
   2:     0x7fffebe6b617 - napi_register_module_v1
   3:     0x7fffebe7ec65 - napi_register_module_v1
   4:     0x7fffebe85149 - napi_register_module_v1
   5:     0x7fffebe84f38 - napi_register_module_v1
   6:     0x7fffebe85a0a - napi_register_module_v1
   7:     0x7fffebe85762 - napi_register_module_v1
   8:     0x7fffebe7ee6f - napi_register_module_v1
   9:     0x7fffebe6738e - napi_register_module_v1
  10:     0x7fffee4a33a5 - wasmer_vm_throw
  11:     0x7fffee4a32f3 - wasmer_vm_throw
  12:     0x7fffee4a3521 - wasmer_vm_throw
  13:     0x7fffee49d2c3 - wasmer_vm_throw
  14:     0x7fffee4028d0 - napi_register_module_v1
  15:     0x7fffee3f9284 - napi_register_module_v1
  16:     0x7ff8b46b1d86 - RtlCaptureContext2
  17:     0x7fffee49d2a7 - wasmer_vm_throw
  18:     0x7fffe929d05d - <unknown>
  19:     0x7fffebe055a4 - napi_register_module_v1
  20:     0x7fffebdfa759 - napi_register_module_v1
  21:     0x7ff816889098 - napi_create_threadsafe_function
  22:     0x7ff81688cb0e - node_module_register
  23:     0x7ff816827f67 - ZN4node17SetCppgcReferenceEPN2v87IsolateENS0_5LocalINS0_6ObjectEEEPv
  24:     0x7ff81688b6f8 - node_module_register
  25:      0x1cc1fdcf64d - <unknown>
  26:      0x1cc1fdcdbd4 - <unknown>
  27:      0x1cc00056fdd - <unknown>
  28:      0x1cc000953ed - <unknown>
  29:      0x1cc00140465 - <unknown>
  30:      0x1cc00093de1 - <unknown>
  31:      0x1cc0009416f - <unknown>
  32:      0x1cc0005447b - <unknown>
  33:      0x1cc0009430f - <unknown>
  34:      0x1cc1fdcdbd4 - <unknown>
  35:      0x1cc1fdcdbd4 - <unknown>
  36:      0x1cc1fef93fd - <unknown>
  37:      0x1cc1fdce4ba - <unknown>
  38:      0x1cc1ff82d81 - <unknown>
  39:      0x1cc1fdcdbd4 - <unknown>
  40:      0x1cc1fdcdbd4 - <unknown>
  41:      0x1cc1fe1113b - <unknown>
  42:      0x1cc1fefae75 - <unknown>
  43:      0x1cc1fdfed47 - <unknown>
  44:      0x1cc1fdcb67b - <unknown>
  45:     0x7ff81708d83e - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  46:     0x7ff81708e7fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  47:     0x7ff81708e8fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  48:     0x7ff8170c43b8 - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  49:     0x7ff8170c47cb - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  50:     0x7ff8167d2aaf - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  51:     0x7ff8167d2d7d - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  52:     0x7ff8168dae78 - ZN4node12OnFatalErrorEPKcS1_
  53:     0x7ff8168e0d21 - ZN4node12OnFatalErrorEPKcS1_
  54:     0x7ff81960e750 - ZN2v84base4bits21RoundUpToPowerOfTwo64Ey
  55:     0x7ff816bd0fa5 - uv_barrier_destroy
  56:     0x7ff816bd5801 - uv_async_send
  57:     0x7ff816bd661f - uv_run
  58:     0x7ff8167d5ee3 - ZN4node22CommonEnvironmentSetup21CreateForSnapshottingEPNS_20MultiIsolate
PlatformEPSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS9_EERKSB_SE_RKNS_14Snaps
hotConfigE
  59:     0x7ff81692dc17 - ZN4node12OnFatalErrorEPKcS1_
  60:     0x7ff81692e21f - ZN4node12OnFatalErrorEPKcS1_
  61:     0x7ff816881ed1 - ZN4node5StartEiPPc
  62:     0x7ff6195b1576 - <unknown>
  63:     0x7ff6195b10c9 - <unknown>
  64:     0x7ff6195b1416 - <unknown>
  65:     0x7ff8b4247374 - BaseThreadInitThunk
  66:     0x7ff8b465cc91 - RtlUserThreadStart
thread caused non-unwinding panic. aborting.

thread '<unnamed>' (13632) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread '<unnamed>' (13632) panicked at library\core\src\panicking.rs:230:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fffebe937b2 - napi_register_module_v1
   1:     0x7fffebe9b98a - napi_register_module_v1
   2:     0x7fffebe6b617 - napi_register_module_v1
   3:     0x7fffebe7ec65 - napi_register_module_v1
   4:     0x7fffebe85149 - napi_register_module_v1
   5:     0x7fffebe84f38 - napi_register_module_v1
   6:     0x7fffebe85a0a - napi_register_module_v1
   7:     0x7fffebe85762 - napi_register_module_v1
   8:     0x7fffebe7ee6f - napi_register_module_v1
   9:     0x7fffebe6738e - napi_register_module_v1
  10:     0x7fffee4a33a5 - wasmer_vm_throw
  11:     0x7fffee4a32f3 - wasmer_vm_throw
  12:     0x7fffee4a3521 - wasmer_vm_throw
  13:     0x7fffee49d2c3 - wasmer_vm_throw
  14:     0x7fffee4028d0 - napi_register_module_v1
  15:     0x7fffee3f9284 - napi_register_module_v1
  16:     0x7ff8b46b1d86 - RtlCaptureContext2
  17:     0x7fffee49d2a7 - wasmer_vm_throw
  18:     0x7fffe929d05d - <unknown>
  19:     0x7fffebe055a4 - napi_register_module_v1
  20:     0x7fffebdfa759 - napi_register_module_v1
  21:     0x7ff816889098 - napi_create_threadsafe_function
  22:     0x7ff81688cb0e - node_module_register
  23:     0x7ff816827f67 - ZN4node17SetCppgcReferenceEPN2v87IsolateENS0_5LocalINS0_6ObjectEEEPv
  24:     0x7ff81688b6f8 - node_module_register
  25:      0x2579fdcf64d - <unknown>
  26:      0x2579fdcdbd4 - <unknown>
  27:      0x25780097d9d - <unknown>
  28:      0x25780091f6d - <unknown>
  29:      0x2578011aae5 - <unknown>
  30:      0x25780123603 - <unknown>
  31:      0x257801169e1 - <unknown>
  32:      0x25780122ea5 - <unknown>
  33:      0x2579fdcdbd4 - <unknown>
  34:      0x2579fdcdbd4 - <unknown>
  35:      0x2579fef93fd - <unknown>
  36:      0x2579fdce4ba - <unknown>
  37:      0x2579ff82d81 - <unknown>
  38:      0x2579fdcdbd4 - <unknown>
  39:      0x2579fdcdbd4 - <unknown>
  40:      0x2579fe1113b - <unknown>
  41:      0x2579fefae75 - <unknown>
  42:      0x2579fdfed47 - <unknown>
  43:      0x2579fdcb67b - <unknown>
  44:     0x7ff81708d83e - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  45:     0x7ff81708e7fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  46:     0x7ff81708e8fc - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  47:     0x7ff8170c43b8 - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  48:     0x7ff8170c47cb - ZN2v88Unwinder8PCIsInV8EyPKNS_11MemoryRangeEPv
  49:     0x7ff8167d2aaf - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  50:     0x7ff8167d2d7d - ZN4node13CallbackScopeC1EPN2v87IsolateENS1_5LocalINS1_6ObjectEEENS_13asyn
c_contextE
  51:     0x7ff8168dae78 - ZN4node12OnFatalErrorEPKcS1_
  52:     0x7ff8168e0d21 - ZN4node12OnFatalErrorEPKcS1_
  53:     0x7ff81960e750 - ZN2v84base4bits21RoundUpToPowerOfTwo64Ey
  54:     0x7ff816bd0fa5 - uv_barrier_destroy
  55:     0x7ff816bd5801 - uv_async_send
  56:     0x7ff816bd661f - uv_run
  57:     0x7ff8167d5ee3 - ZN4node22CommonEnvironmentSetup21CreateForSnapshottingEPNS_20MultiIsolate
PlatformEPSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS9_EERKSB_SE_RKNS_14Snaps
hotConfigE
  58:     0x7ff81692dc17 - ZN4node12OnFatalErrorEPKcS1_
  59:     0x7ff81692e21f - ZN4node12OnFatalErrorEPKcS1_
  60:     0x7ff816881ed1 - ZN4node5StartEiPPc
  61:     0x7ff6195b1576 - <unknown>
  62:     0x7ff6195b10c9 - <unknown>
  63:     0x7ff6195b1416 - <unknown>
  64:     0x7ff8b4247374 - BaseThreadInitThunk
  65:     0x7ff8b465cc91 - RtlUserThreadStart
thread caused non-unwinding panic. aborting.

Provide environment information

# npx next info

thread '<unnamed>' (20708) panicked at C:\Users\Administrator\.cargo\registry\src\index.crates.io-19
49cf8c6b5b557f\napi-sys-2.4.0\src\functions.rs:7:3:
Node-API symbol has not been loaded

Cannot execute it due to the same error. But the key enviroment should be mingw64.

Which area(s) are affected? (Select all that apply)

create-next-app

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

Additional context

I believe it's a upstream issue about mingw's binutils and MSVC. But I couldn't find the right place to create the issue and link it. Maybe someone can help to create a issue there. Originally, https://github.com/nodejs/node/issues/38782

extent analysis

Fix Summary

The panic is caused by the Rust napi-sys crate (used by Next.js’ SWC compiler

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Next.js can't work with the mingw nodejs [1 comments, 2 participants]