Skip to content
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

🚀 Feature: Add Vitest VS Code Extension to extensions.json? #1628

Closed
2 tasks done
johnnyreilly opened this issue Aug 14, 2024 · 3 comments · Fixed by #1630
Closed
2 tasks done

🚀 Feature: Add Vitest VS Code Extension to extensions.json? #1628

johnnyreilly opened this issue Aug 14, 2024 · 3 comments · Fixed by #1630
Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request

Comments

@johnnyreilly
Copy link
Collaborator

johnnyreilly commented Aug 14, 2024

Bug Report Checklist

Overview

I wanted to be able to run tests in VS Code. For that I found I needed to install the Vitest VS Code extension. I made the following change to my own projects extensions.json to recommend this to users:

+  "vitest.explorer"

Would it be worth including that in CTA for users writing tests?

Additional Info

No response

@johnnyreilly johnnyreilly added the type: feature New enhancement or request label Aug 14, 2024
@JoshuaKGoldberg
Copy link
Owner

Oh hey this is pretty sweet! I'd missed it. Yeah, yes please!

@JoshuaKGoldberg JoshuaKGoldberg added the status: accepting prs Please, send a pull request to resolve this! label Aug 14, 2024
@johnnyreilly
Copy link
Collaborator Author

Implementing now - fun fact: GitHub CoPilot suggested @orta's "orta.vscode-jest" before I got to the "vitest.explorer" 😄

Copy link

🎉 This is included in version v1.70.0 🎉

The release is available on:

Cheers! 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants