Unbound Breakpoint using debugger

[musician2000]

Summary

When developing a raycast extention and using the debugger in vscode, any breakpoint set doesn't work and shows "unbound breakpoint"

Steps to reproduce

creating an extention in vscode
running npm run dev which starts correctly
choose a breakpoint
then run in vscode attach raycast debugger

What is the current bug behavior?

It shows Unbound breakpoint see screenshot

What is the expected correct behavior?

For it to not show this error and work as a normal breakpoint

Relevant logs and/or screenshots

Possible fixes

[qmg-krewera]

I'm experiencing the same issue. When attaching the debugger, the progress bar indicator is displayed for some time and then disappears and no error or warning is displayed. After that there's no material change to VSCode behaviour after the attempt suggesting that the debugger actually got attached to the process.

[slavarazum]

Yep, debugging currently doesn't attach to the dev process.