Skip to content

What's New

In addition to this page, you may also follow us on twitter (@WallabyJs) to be notified whenever we release notable features.

Most Recent Major Features and Changes

The What’s New section includes major features and changes that have been made in the last 12-18 months. For older news or more details about minor updates and changes, please refer to our changelog.

Log Copying Improvements (Aug 14 2025)

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.

Read more

VS Code Coverage Improvements (Jul 31 2025)

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.

Read more

Angular v20 support (Jul 25 2025)

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.

Improved Side-by-Side and Compact Diffs for Jest/Vitest Asymmetric Matchers (Jul 01 2025)

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.

Automatic Node.js Version Selection Based on Project Configuration (Jun 30 2025)

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.

Major Performance Improvements (Jun 17 2025)

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.

Previous major features and changes

Our what’s new archive contains the full history of our major features and changes (starting February 2020).

Full Change Log

Our changelog is available in our public repository. Please note that while we update our changelog every few months, we release new versions of Wallaby.js a few times a week (sometimes a few times a day).

Are we missing something? Share your idea or vote for other submitted ideas