v3.0.1

Fixed

• Non-Yarn workspaces no longer result in a stall due to an infinite loop. (af87fa7)
• Corrected path to buildArgv function in jest-cli dependency after it was moved in Jest 29.2.1. (7ac716a)

Full Changelog: v3.0.0...v3.0.1

v3.0.0

Breaking Changes

• Dropped support for Node.js 14.x and 16.13.x, VS Code <1.71.0, and Jest <29.0.0. (f779c3a)

Changed

• The VS Code extension host is no longer killed when the test run is finished. (91d6743)
• The package now specifies to Yarn that it should be unplugged to allow VS Code to start using the package's entry point in a PnP environment. (bf17692)

Full Changelog: v2.2.0...v3.0.0

v2.2.0

Added

• Environments using Yarn PnP are now supported. (#46)
• All options from the parent Jest runner are now passed to the child runner. (f300e64)
• VS Code process information and download progress can now be suppressed using the quiet option. (f300e64)

Changed

• A less internal API is now used to start the child instance of Jest. (6196f24)

Fixed

• Tests in nested directories no longer result in the runner expecting and failing tests from a different directory that are not yet queued. (f300e64)

v2.1.0

Added

• Test results are now reported per test file instead of per folder. (#26)
• Console output can now be filtered to output made by tests that use console.log, .error, .warn, .info, or .dir. (#43)

Changed

• Communication between VS Code and Jest is now handled using an IPC channel instead of using the standard output of the VS Code process. (0c98677)

v2.0.0 — First Release!

First release of jest-runner-vscode! 🎉

Commit History