Prisma•2w ago

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

5 Replies

Prisma AI Help•2w ago

You decided to hold for human wisdom. We'll chime in soon! Meanwhile, #ask-ai is there if you need a quick second opinion.

enzito•2w ago

https://github.com/su-its/core/pull/35 This was a quick fix that I tried and it worked for me, I still haven't found the correct one btw

GitHub

prisma のバージョンを固定 by KikyoNanakusa · Pull Reque...

やったこと prisma のバージョンをDev以外でも固定なぜ prisma 6.6.0で破壊的な変更が加えられ, 動作に支障が生じたため. 参考 prisma/prisma#26840

Nurul•2w ago

Hey 👋 I was able to find this issue with similar error https://github.com/prisma/prisma/issues/26839

GitHub

Issues with Prisma 6.6.0 · Issue #26839 · prisma/prisma

Bug description Since the release of Prisma 6.6.0 I have been experiencing issues after generating new models: thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/en...

Nurul•2w ago

Does this comment help?

GitHub

Issues with Prisma 6.6.0 · Issue #26839 · prisma/prisma

Bug description Since the release of Prisma 6.6.0 I have been experiencing issues after generating new models: thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/en...

ToothyOP•3d ago

I'll have to see if I can work with this - I was using pnpm dlx instead of exec and this might be it, although i never updated Prisma :monkaHmm: Thanks for the response!

Gaming

Programming

Sudden issues after trying to access localhost with my nextjs app - no changes in code.

Did you find this page helpful?