What's New
We’re proud to introduce Wallaby v3, an overhauled engine that streams test, coverage, log, and error results in real time. Wallaby v3 starts instantly with cached results, prioritizes execution of the files you’re working on, and keeps you updated with progress and time estimates. Read more in our blog.
The Wallaby overview panel now lets you toggle between a list of failing tests and the full test tree. The same actions and keyboard shortcuts work in both views.
Wallaby’s Coverage view is now automatically filtered based on smart start, selected or focused tests. This makes it easy to concentrate on relevant parts of your project and avoid noise from unrelated or uncovered files.
Wallaby Logs now provide a convenient way to copy values and paths from log entries. This feature allows both root level and nested values to be quickly copied or identified. This is particularly useful when working with object hierarchies and array elements. These new copy actions are available through keyboard shortcuts and a new context menu.
Wallaby for VS Code now shows file-level code coverage directly in the Explorer View and the Test Coverage View. This makes it easier to spot what’s covered (and what isn’t) at a glance.
Angular CLI v20 introduces a significant update: esbuild is now the default build system, replacing webpack. Wallaby now fully supports Angular CLI v20, enabling seamless testing for projects using either @angular/build:karma or legacy @angular-devkit/build-angular:karma configurations.
Wallaby now renders cleaner, more readable diffs for Jest and Vitest tests using asymmetric matchers like expect.any(), expect.objectContaining(), and expect.stringContaining(). Instead of showing verbose raw matcher code, Wallaby displays intuitive labels like Anything<String> or StringContaining "hello" in side-by-side and compact views, making it easier to spot what actually failed without losing access to full actual/expected values for copying or inspection.
Wallaby now automatically detects and selects the appropriate Node.js version for your project based on configuration files like .nvmrc, .node-version, package.json (engines.node field), and more. When multiple Node.js versions are installed on your system, Wallaby intelligently chooses the version that matches your project’s requirements using existing version managers (e.g. nvm, volta, fnm, asdf, etc.). This eliminates the need for manual configuration and ensures your tests run in the correct Node.js environment without any additional setup.
In the last few released versions, we’ve made major Wallaby.js performance improvements: faster incremental runs, better handling of compute-heavy and path-rich tests, and quicker startup for small projects. We now pass metadata incrementally, use ~10x-12x less CPU and memory for code insights, and avoid spawning unnecessary workers.
Wallaby now supports the latest version of Jest v30.0.x+. The recent update of Jest included breaking changes that required updates to Wallaby’s Jest integration.
