Repository navigation
Replies: 5 comments 1 reply
|
Hi @sryeddula 👋 |
|
I am also receiving while building the application 70 ? NexusPrismaInputs[ModelName][MethodName][InputName] 132 GetNexusPrismaInput<ModelName, MethodName, 'filtering'>, 140 GetNexusPrismaInput<ModelName, MethodName, 'ordering'>, |
|
Getting similar errors when trying to build: |
|
Il semble que vous rencontriez deux problèmes principaux. Premièrement, concernant le problème de débogage dans VSCode, il semblerait que le point d'arrêt ne soit pas atteint lors de l'exécution de la requête. Cela peut se produire si le serveur de développement Du côté des erreurs TypeScript, les problèmes semblent liés aux types Nexus Prisma, en particulier au type |
|
Your configuration looks mostly correct, but the issue may be that Nexus starts a child Node.js process for your application, and VS Code isn’t attaching the debugger to it. Try adding "autoAttachChildProcesses": true and "skipFiles": ["<node_internals>/**"] to your configuration. Also, make sure source maps are generated and the breakpoint is set in the actual TypeScript source used by the running app. If it still doesn’t stop, try "stopOnEntry": true to confirm the debugger is attached. Debugging is a bit like troubleshooting a casino game: you need to identify exactly where the process goes https://7-bitcasino.net/ wrong. |
Uh oh!
There was an error while loading. Please reload this page.
I am using following config for debugging in vscode as per documentation. When I added breakpoint on a query resolver its not breaking during query execution
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Debug Nexus App",
"protocol": "inspector",
"runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nexus",
"runtimeArgs": ["dev"],
"sourceMaps": true,
"console": "integratedTerminal"
}
]
}
All reactions