Tobias Hernstig
Tobias Hernstig
@mrazauskas close this thread then? Or is it a docs issue?
@mrazauskas sorry for asking, but I am a bit confused as to the conclusion of this now. Is the suggestion for everyone to switch to jest-light-runner. Considering that Node assert...
Comment. Still a bug.
@aslushnikov Maybe I am missing something, but how does this work if I execute a `page.screenshot()` as a custom handling when failures happen? Or if I use the record functionality,...
@aslushnikov great :) No idea of how you achieved this with the inspector, but hopefully you can re-use some of that code for also this scenario we described i.e. in...
@klhex that was linked from the original post, and if you look closely you will notice that it is @aslushnikov who has written it 😛
@gcampbell-msft I want to add that even news like https://code.visualstudio.com/updates/v1_94#_start-debugging-from-chat-experimental most likely will not work well with the custom debug experience.
@gcampbell-msft For all intents and purposes I think people do get thrown of by the custom/hidden debugging experience if not seeing it in the launch.json file. As explained in the...
> Maybe vs code need some launch.d/*json mechanics to allow tool dynamic generator launch safely works! The common way VS Code implements things like this is by naming convention of...
> If the cursor follows immediately a word which is a path to an existing dir, fzf this dir instead of the current. Do I understand this correctly? You intend...