v0.5.1

   🐞 Bug Fixes

• Correctly find all test files  -  by @sheremet-va (0073e)

    View changes on GitHub

v0.5.0

This is a complete rewrite of a Vitest VSCode extension. All minor odd versions are considered a pre-release. You can use this version and give us feedback by switching to a pre-release version:

   🚨 Breaking Changes

• Use Vitest public API instead of Vitest CLI  -  by @sheremet-va in #253 (0b70c)
  • Requires Vitest 1.4.0 or higher
  • Faster test execution (instant feedback when clicking on "start")
  • Better continues mode integration
  • Support for "each" tests
  • Support in-source tests

    🐛 Known Issues

• Currently, the extension requires vite.config or vitest.config file to function
• The "continues" mode doesn't update test results if several test functions are selected - it will use the last one selected. For now, you can use continues mode on a file without problems
• Sometimes debugger starts only on a second try
• When using debugger, tests are not marked as "enqueued"
• Update snapshot is not implemented, but button exists (does nothing)

    View changes on GitHub

v0.4.1

   🐞 Bug Fixes

• Use precise regexp pattern for vitest run args  -  by @keroxp in #263 (01577)
• Reference VS Code settings when determining vitest version  -  by @cameronbrill in #269 (3c126)

    View changes on GitHub

v0.4.0

   🚨 Breaking Changes

• Disabling continuous mode prevents future tests from being run  -  by @ffMathy in #258 (75d78)

   🐞 Bug Fixes

• Don't show error notification if version is not known  -  by @sheremet-va (dc9fb)

    View changes on GitHub

v0.3.1

   🚀 Features

• Support .each suite execution by regex  -  by @keroxp in #214 (4ceb4)

   🐞 Bug Fixes

• Include pattern not supported  -  by @ffMathy and @sheremet-va in #250 (e02ee)
• Don't use DOM types  -  by @sheremet-va in #252 (f3c36)

    View changes on GitHub