New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add vitest-dev/vscode
#12
Conversation
Run & review this pull request in StackBlitz Codeflow. |
I verified the CI on my fork:
Actually it looks flaky. For now, I added retry and it looks better, but I might need to dig into this. |
This PR adds Vitest VS Code extension https://github.com/vitest-dev/vscode.
Little summary of the repo and tests:
@vitest/ws-client
https://github.com/vitest-dev/vscode/blob/85aa7edfce24914bee6a849e61d935e8f0b97bb2/src/pure/watch/ws-client.ts and uses it to communicate with Vitest CLI spawned by--api
(though this might change in the future by feat: use Vitest public API instead of Vitest CLI vscode#253)pnpm test
(added in feat: switch to vs code tests vscode#262) only tests internal utilities, so it doesn't really exercise Vitest feature.pnpm test-e2e
(will be added in test: setup vscode-e2e vscode#276) runs a simple sample with extensions, so this will exercise both extension's ws-client implementation and Vitest CLI.I think we can wait this PR until E2E is setup on vscode extension repo, but I just wanted to explore ecosystem-ci beforehand.