Ok, i am kind of able to debug now. I figured, that i had to compile the typescript and start with the dist/index.js, now i can set breakpoints on starting the server. But unfortunatelly, the playground does not get started this way. I figured that I somehow had to start it before/parallel but I did not come up with a solution yet. In Webstorm you can run a npm script before a debug session or you can pass parameters to node. Running the npm script before does just start the server without debugging (wich makes sense). So I tried to use the node parameters like “node_modules/npm-run-all --parallel graphql playground” for example. But all that does is to start debugging and ending the process right afterwards. I am also not sure what node expects as parameter, so i might be doing something wrong. On localhost:4000 there is nothing running, but on the http://localhost:4466/backend/dev I get a message, that my token is invalid. So i changed the URL in the field to localhost:4000 and could query my backend. But then, the breakpoint where not hit again, so I am thinking that I am on some other process again. I am just not able to wrap my head around all this.
Did nobody ever debug a prisma application so far? Maybe I am oldschool, too, but I was expecting that in the JS world debugging in an IDE is something that you would do
Is there an option to run the playground independent from the server? That might actually help