Replies: 1 comment
-
|
Due to the debugger step-in-to-code ending up at the wrong line we had to shelve our entire migration to bun. It was essentially done and ready to merge, but if we can't debug our code, we don't want to move to any bun solutions. If this can get some attention, we can move ahead. I'll check back to see if there is anything I can offer or test, but for now I have to move on; suffering through Jest, npm install, etc. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
It took me most of a day to figure out a workaround to make the Bun for Visual Studio Code extension work with the Cursor test explorer / debugger. I have a wrapper script that demonstrates a fix that could easily be used to fix the extension itself. I also have an ongoing issue with it generating breakpoints at the first line in a test
it()even with the setting to stop on first line OFF (and a bad workaround to sort of get past it but not really).I would love to share details and help improve bun. Where should I go to do this?
Beta Was this translation helpful? Give feedback.
All reactions