I keep having an issue after I close a browser instance started with the Playwright extension, then close and reopen VSCode, it complains about not being able to read the config file.
at Ve._treeItemSelected (c:\Users\***\.vscode\extensions\ms-playwright.playwright-1.0.16\out\extension.js:109:520) at s.value (c:\Users\***\.vscode\extensions\ms-playwright.playwright-1.0.16\out\extension.js:91:4664) at c.z (c:\Users\***\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:80:1902) at c.fire (c:\Users\***\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:80:2119) at St._poll (c:\Users\***\.vscode\extensions\ms-playwright.playwright-1.0.16\out\extension.js:110:727``` I noticed when I uninstall the extension, there's some noise in the Extension Host output about the host terminating stuff that shouldn't be running and require termination. ```2023-10-16 12:29:00.946 [info] Extension host terminating: renderer closed the MessagePort 2023-10-16 12:29:00.966 [error] Canceled: Canceled at new g (c:\Users\***\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:57216) at i.U (c:\Users\***\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:134:10864) ... at MessagePortMain.emit (node:events:513:28) at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367) setContext undefined``` It seems to be causing issues with the Playwright UI mode too so I'm not sure what to think.
This thread is trying to answer question "Is there a bug in the VSCode extension or am I misunderstanding something?"
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email firstname.lastname@example.org.