Toothy
Toothy
Explore posts from servers
PPrismaTTCTheo's Typesafe Cult
PostsComments
PPrisma
Created by Toothy on 4/9/2025 in #help-and-questions
Sudden issues after trying to access localhost with my nextjs app - no changes in code.
Hey! I randomly started getting this after running pnpm run dev to start my dev environment - it shows up after I actually try to enter the website. I did no changes to code whatsoever, it just started happening. I am using prisma client and prisma 5.17 and nextjs 14.2.25 - I was wondering if anybody here might have a clue on what could have happened? I don't know what more info I could provide right away so just ask away if needed. Thanks in advance 
 ✓ Compiled / in 1761ms (748 modules)

thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/engine.rs:76:45:

            Failed to deserialize constructor options.

            This usually happens when the javascript object passed to the constructor is missing
            properties for the ConstructorOptions fields that must have some value.

            If you set some of these in javascript through environment variables, make sure there are
            values for data_model, log_level, and any field that is not Option<T>
            : Error { status: InvalidArg, reason: "missing field `enableTracing`", maybe_raw: 0x0 }
stack backtrace:
   0:        0x168880360 - _napi_register_module_v1
   1:        0x1680e9968 - <unknown>
   2:        0x16887f1a4 - _napi_register_module_v1
   3:        0x168880220 - _napi_register_module_v1
   4:        0x16887ef58 - _napi_register_module_v1
   5:        0x1688a56c8 - _napi_register_module_v1
   6:        0x1688a5638 - _napi_register_module_v1
   7:        0x1688a5e5c - _napi_register_module_v1
   8:        0x168c640a8 - _napi_register_module_v1
   9:        0x168c64368 - _napi_register_module_v1
  10:        0x168076f40 - <unknown>
  11:        0x168070aa0 - <unknown>
fatal runtime error: failed to initiate panic, error 5
 ✓ Compiled / in 1761ms (748 modules)

thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/engine.rs:76:45:

            Failed to deserialize constructor options.

            This usually happens when the javascript object passed to the constructor is missing
            properties for the ConstructorOptions fields that must have some value.

            If you set some of these in javascript through environment variables, make sure there are
            values for data_model, log_level, and any field that is not Option<T>
            : Error { status: InvalidArg, reason: "missing field `enableTracing`", maybe_raw: 0x0 }
stack backtrace:
   0:        0x168880360 - _napi_register_module_v1
   1:        0x1680e9968 - <unknown>
   2:        0x16887f1a4 - _napi_register_module_v1
   3:        0x168880220 - _napi_register_module_v1
   4:        0x16887ef58 - _napi_register_module_v1
   5:        0x1688a56c8 - _napi_register_module_v1
   6:        0x1688a5638 - _napi_register_module_v1
   7:        0x1688a5e5c - _napi_register_module_v1
   8:        0x168c640a8 - _napi_register_module_v1
   9:        0x168c64368 - _napi_register_module_v1
  10:        0x168076f40 - <unknown>
  11:        0x168070aa0 - <unknown>
fatal runtime error: failed to initiate panic, error 5
6 replies
TTCTheo's Typesafe Cult
Created by Toothy on 8/30/2024 in #questions
Huge memory usage spikes with uploadthing, seeking help on how to handle it.
No description
7 replies