-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Is the project dead? #207
Comments
I'm concerned too because for some reason the extension is broken and endlessly runs on the CPU. If left unchecked, it drains my battery by 25% in just 15 minutes. This is really bad! |
I have started a fork in https://github.com/MilanKovacic/vitest-visual-studio-code-extension. Once original maintainer returns to the project, we can integrate the changes back. Currently, I just performed very quick upgrades to make it compatible with latest vitest. If anyone else is interested in contributing, feel free to join the effort. |
@zxch3n a few words from you would be appreciated |
Thank you @MilanKovacic this is really helpful we switched from jest to vitest recently and my dev experience was suffering greatly |
Hello! @zxch3n has been busy for some time now with his own projects, but Vitest team is looking into reviving this repo - feel free to join Discord to discuss the extension: https://discord.gg/Bc5rk88F |
Vitest has been pushing a lot of updates lately, including the first stable release, but the extension is now almost entirely broken, and despite the new issues, it seems there are really no updates lately (at least since July).
The text was updated successfully, but these errors were encountered: