Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] VS Code extension not working
See original GitHub issueContext:
- Playwright Version: 1.15.2
- Extension version: v0.0.7
Describe the bug
Test explorer does not appear when viewing test files with extension *.spec.ts
Output window log
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Visual Studio Code extensions stopped working suddenly
Open the command palette ( Ctrl + Shift + P ) · Run Disable All Installed Extensions · Then run Enable All Extensions...
Read more >Managing Extensions in Visual Studio Code
Discover, add, update, disable and uninstall Visual Studio Code extensions (plug-ins) through the Extension Marketplace.
Read more >Extensions issues after update to vscode 1.47.0 #102082
Open VS Code and make sure extensions are loaded and running. Check extensions view and running extensions editor. Also check console for no ......
Read more >Extension for Visual Studio Code - Sorbet
If the file is typed, Sorbet is "Idle", and hover isn't working, try to reproduce the problem on https://sorbet.run and file a bug...
Read more >Troubleshooting - Visual Studio Live Share - Microsoft Learn
VS Code, A "Dependencies could not be installed" error appears the while extension is finishing installation on first start or you get ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@mxschmitt Thanks, 0.0.9 now works for me.
@PeterHewat thats for the investigation! Indeed, we have changed the CLI path in @playwright/test in version 1.16 which broke the extension.