You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For VS Code, we are building a way to run unit tests in "serverless"/web mode on browsers. To enable debugging in this scenario, we need to either have playwright attach to the browser the js-debug launches (which I hacked together but sometimes fails and is not recommended) or have js-debug attach to playwright's browser.
Playwright has a launchServer option already. If the launched server exposed a /json/list endpoint roughly compatible with the one Chromium publishes, we'd be able to attach to it. Or, if there was some other way to ask the browser to set up a --remote-debugging-port on a specific port number.
For VS Code, we are building a way to run unit tests in "serverless"/web mode on browsers. To enable debugging in this scenario, we need to either have playwright attach to the browser the js-debug launches (which I hacked together but sometimes fails and is not recommended) or have js-debug attach to playwright's browser.
Playwright has a
launchServer
option already. If the launched server exposed a/json/list
endpoint roughly compatible with the one Chromium publishes, we'd be able to attach to it. Or, if there was some other way to ask the browser to set up a--remote-debugging-port
on a specific port number.For additional discussion and context, see https://github.com/microsoft/vscode-internalbacklog/issues/2235#issuecomment-875017195
The text was updated successfully, but these errors were encountered: