trigger.dev icon indicating copy to clipboard operation
trigger.dev copied to clipboard

improve v3 debug experience

Open mulyoved opened this issue 7 months ago • 0 comments

In v2 I used to connect my nextjs app to debugger and let it run, when I want to debug some code I can just set break point in code and re-run the job as much as I want until I solve the issue

in v3 this is not working so well

starting with npx trigger.dev@beta dev --debugger

problem 1 Seem that debugger start with something like --inspect-brk for every task that run I need to switch to VSCode and press F5 for the task to start run

problem 2 If I have event that start many tasks at the same time, or task that cause the run of other task like in my use case, database change cause webhook, that change other systems that trigger more webhooks, all those are separate tasks, in v3 it is impossible to catch and debug the part I care about as each task start in a new nodejs process

Will be great if we can improve the DX around debugging tasks and maybe have a debug mode where all tasks run on one nodejs process

Again, this was working fine on v2 as jobs where running on the one nextjs process

mulyoved avatar Jul 09 '24 08:07 mulyoved