Releases: vitest-dev/vscode
Releases · vitest-dev/vscode
v0.5.8
🐞 Bug Fixes
- Don't start ws connection - by @sheremet-va (78a2e)
- Refresh package.json state when installing a new version - by @sheremet-va (3c3f4)
- Collect tests when the vscode is opened with a visible test file - by @sheremet-va (12069)
- Correctly track continuous requests - by @sheremet-va in #315 (d7290)
View changes on GitHub
v0.5.7
🐞 Bug Fixes
- Set env vars
TEST
,VITEST
, andNODE_ENV
- by @hi-ogawa in #309 (80b29) - Don't show the error twice - by @sheremet-va (f05a7)
- Correctly resolve folder id - by @sheremet-va (204d1)
View changes on GitHub
v0.5.6
🐞 Bug Fixes
- Don't queue folders since they are queued automatically - by @sheremet-va (9b489)
- Run correct profile if several profiles are created - by @sheremet-va (881b3)
- Do not create a separate Vitest instance if vitest config overrides vite config - by @sheremet-va (01488)
View changes on GitHub
v0.5.5
🐞 Bug Fixes
- Show errors during collection - by @sheremet-va (44204)
- Show task errors during collection - by @sheremet-va (78681)
- Enqueue test items - by @sheremet-va (ac19e)
- Correctly delete test from the tree when all tests are removed - by @sheremet-va (2d2c5)
- Improve recursive delete when file is removed - by @sheremet-va (3b526)
- Support the same file in different projects - by @sheremet-va (1cea5)
View changes on GitHub
v0.5.4
🚀 Features
- Add a warning when multiple config files found - by @sheremet-va (2fac4)
🐞 Bug Fixes
- Rebuild the extension if vitest.workspace is changed - by @sheremet-va (ecedd)
- Strip ansi from test results - by @sheremet-va (27068)
- Create only a single watcher if multiple configs are in the same folder - by @sheremet-va (ed617)
- Provide process.env when spawning Vitest API - by @sheremet-va (b4b59)
- Disable warning in a workspace folder config, not in the root config - by @sheremet-va (fe2d1)
View changes on GitHub
v0.5.2
🐞 Bug Fixes
- Correctly resolve Vitest that uses workspace feature - by @sheremet-va (29831)
View changes on GitHub
v0.5.1
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
orvitest.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
🐞 Bug Fixes
- Don't show error notification if version is not known - by @sheremet-va (dc9fb)