<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wallaby.js - What's New</title>
    <description>Latest updates and news from Wallaby.js</description>
    <link>https://wallabyjs.com/whatsnew/</link>
    <atom:link href="https://wallabyjs.com/wallaby/rss.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Fri, 17 Apr 2026 05:31:18 +0000</pubDate>
    <lastBuildDate>Fri, 17 Apr 2026 05:31:18 +0000</lastBuildDate>
    <generator>Jekyll v3.9.0</generator>
    
    
      <item>
        <title>Support for Vitest v4.1.4+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v4.1.4+). The recent
update of vitest included major breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v4.1.4.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v4.1.4.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v4.1.0+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v4.1.0+). The recent
update of vitest included major breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v4.1.0.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v4.1.0.html</guid>
        
      </item>
    
      <item>
        <title>Angular v21 Support with Vitest</title>
        <description>&lt;p&gt;For Angular CLI v21 workspaces and projects, Wallaby now automatically detects and configures the default Vitest runner. Wallaby runs tests in Node.js environments such as &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;jsdom&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;happy-dom&lt;/code&gt;, or in browsers via &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;playwright&lt;/code&gt; or &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;webdriverio&lt;/code&gt;, and provides better incremental run performance, reliability, and &lt;a href=&quot;/docs/features/streaming-caching/#result-streaming&quot;&gt;live results streaming&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Wallaby also adds experimental support for &lt;a href=&quot;https://github.com/voidzero-dev/oxc-angular-compiler&quot;&gt;Oxc Angular Compiler&lt;/a&gt;. If you have the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@oxc-angular/vite&lt;/code&gt; package installed, Wallaby will automatically use it to transform your TypeScript Angular files, providing an alternative transpiler that may offer improved performance for certain projects.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;/docs/integration/angular.html#angular-cli-v21&quot;&gt;Read more in the docs&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/angular-v21-vitest-support.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/angular-v21-vitest-support.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest Browser Mode</title>
        <description>&lt;p&gt;Wallaby now supports running Vitest v4.x+ in browser mode, using either the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;playwright&lt;/code&gt; or &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;webdriverio&lt;/code&gt; providers. Wallaby will run your browser instances in headless mode by default (overridable by setting &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;headless: false&lt;/code&gt; in your vitest config).&lt;/p&gt;
</description>
        <pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-vitest-browser-mode.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-vitest-browser-mode.html</guid>
        
      </item>
    
      <item>
        <title>Zen Mode: Control In-Editor Feedback 🧘‍♂️</title>
        <description>&lt;p&gt;We’re excited to introduce &lt;strong&gt;Zen Mode&lt;/strong&gt;, a new Wallaby.js feature that gives you control over when you see
test feedback in your editor.&lt;/p&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/zen-mode.png&quot; /&gt;
&lt;/p&gt;

&lt;p&gt;Coverage indicators and inline error messages are valuable, but when you’re
making lots of changes or typing quickly, instant visual feedback can become distracting. Zen Mode lets you
hide these indicators while Wallaby continues to run tests in the background, so you can review the results
when you’re ready.&lt;/p&gt;

&lt;p&gt;You can easily toggle Zen Mode on and off using the new Toggle Zen Mode command. Simply open the command
palette and search for “Wallaby.js: Toggle Zen Mode” to control when you want to see coverage and error
feedback in the editor. Your Zen Mode preference is stored per project and survives Wallaby restarts, so you
don’t need to reconfigure it every time you start working.&lt;/p&gt;

&lt;p&gt;In addition to the command palette, you can toggle Zen Mode directly from the Overview panel. The panel also
provides quick access to configure &lt;strong&gt;Run Mode&lt;/strong&gt; settings (&lt;strong&gt;Automatic&lt;/strong&gt; / &lt;strong&gt;On Save&lt;/strong&gt;), which also
persist per project and survive restarts.&lt;/p&gt;

&lt;p&gt;With Zen Mode, Run Mode settings, and Pause command, you have more control over your testing workflow,
allowing you to choose the right balance between uninterrupted coding flow and immediate test feedback based
on your current needs.&lt;/p&gt;
</description>
        <pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/zen-mode.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/zen-mode.html</guid>
        
      </item>
    
      <item>
        <title>MCP Support for JetBrains Editors</title>
        <description>&lt;p&gt;Wallaby’s MCP server tools are now available in JetBrains editors. Read more about how to enable it in our &lt;a href=&quot;https://wallabyjs.com/docs/features/mcp/?editor=jb&quot;&gt;docs&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Mon, 24 Nov 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jb-mcp.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jb-mcp.html</guid>
        
      </item>
    
      <item>
        <title>Peek source code anywhere with dot</title>
        <description>&lt;p&gt;Wallaby UI now supports peeking into source code locations directly from various views, including the Test list and Test
tree, Error panels, Logs list, etc. Pretty much any UI element that has a source code location associated with it will
now allow you to peek into the source code without navigating away from your current context. To use the feature,
&lt;strong&gt;simply press the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;.&lt;/code&gt; key&lt;/strong&gt; when focused on an item with a source location.&lt;/p&gt;
</description>
        <pubDate>Tue, 11 Nov 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/dot-peek.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/dot-peek.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v4.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v4.x+). The recent
update of vitest included major breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v4.0.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v4.0.html</guid>
        
      </item>
    
      <item>
        <title>AI Action Selector</title>
        <description>&lt;p&gt;We have added a mode selector to Wallaby Copilot integration, allowing you to choose between different modes of operation, such as &lt;strong&gt;Investigation&lt;/strong&gt;, &lt;strong&gt;Analytical Fix&lt;/strong&gt; and &lt;strong&gt;Direct Fix&lt;/strong&gt;. This provides more flexibility in how the Copilot prompt is generated and what level of detail is provided to the AI model. We have also added code lens action for failing tests to quickly switch between modes.&lt;/p&gt;
</description>
        <pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/ai-selector.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/ai-selector.html</guid>
        
      </item>
    
      <item>
        <title>Vitest Improvements</title>
        <description>&lt;p&gt;Wallaby’s v3 release shipped with some large-scale changes to our Vitest integration. These changes shift responsibility
for determining test execution order from Vitest to Wallaby and provide a more responsive test execution experience.
Since the release, we have made several changes to improve performance and reliability for issues that could affect
larger projects. We’re continuing to work on further enhancements to make Wallaby and Vitest work even better together.&lt;/p&gt;
</description>
        <pubDate>Mon, 20 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-improvements.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-improvements.html</guid>
        
      </item>
    
      <item>
        <title>Identifier Expressions Logging</title>
        <description>&lt;p&gt;We have updated Wallaby to log multiple values for
&lt;a href=&quot;https://wallabyjs.com/docs/features/advanced-logging/#identifier-expressions&quot;&gt;identifier expressions&lt;/a&gt; (i.e., variable
names), limiting the number of logged values and traversal depth, while clearly indicating when the count limit is
reached. Previously, a single value was logged for identifier expressions, which could lead to incomplete or misleading
information.&lt;/p&gt;
</description>
        <pubDate>Sat, 18 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/identifier-expressions-logging.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/identifier-expressions-logging.html</guid>
        
      </item>
    
      <item>
        <title>Angular 20 Workspaces</title>
        <description>&lt;p&gt;In Angular workspaces, each project’s tests now run in their own dedicated browser instance, providing improved
isolation between test environments. This change eliminates shared state and unintended side effects across projects,
resulting in more reliable and consistent test results. It also ensures that project-specific configurations and
dependencies are evaluated independently, making the test behavior more closely aligned with &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;ng test&lt;/code&gt;.&lt;/p&gt;
</description>
        <pubDate>Thu, 16 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/angular-v20-workspaces-support.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/angular-v20-workspaces-support.html</guid>
        
      </item>
    
      <item>
        <title>Navigation Target Selector</title>
        <description>&lt;p&gt;We have added a navigation target selector to error navigation actions in Wallaby Overview and Side views. You can now
quickly choose the exact location of a failing test error to navigate to, such as the &lt;strong&gt;test definition&lt;/strong&gt;, &lt;strong&gt;assertion
failure&lt;/strong&gt;, or &lt;strong&gt;source code line&lt;/strong&gt;.&lt;/p&gt;
</description>
        <pubDate>Fri, 10 Oct 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/nav-selector.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/nav-selector.html</guid>
        
      </item>
    
      <item>
        <title>Introducing Wallaby v3</title>
        <description>&lt;p&gt;We’re proud to introduce &lt;strong&gt;Wallaby v3&lt;/strong&gt;, 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. &lt;a href=&quot;/blog/wallaby-v3.html&quot;&gt;Read more in our blog&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Fri, 26 Sep 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/wallaby-v3.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/wallaby-v3.html</guid>
        
      </item>
    
      <item>
        <title>Test Explorer in Overview panel</title>
        <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/vscode-overview-test-explorer.gif&quot; /&gt;
&lt;/p&gt;

&lt;p&gt;You can hide the filter control to save vertical space. Your filter value is preserved across Wallaby restarts.&lt;/p&gt;
</description>
        <pubDate>Tue, 23 Sep 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/test-explorer-in-overview.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/test-explorer-in-overview.html</guid>
        
      </item>
    
      <item>
        <title>Coverage View Improvements</title>
        <description>&lt;p&gt;Wallaby’s Coverage view is now automatically filtered based on
&lt;a href=&quot;https://wallabyjs.com/docs/features/smart-start/&quot;&gt;smart start&lt;/a&gt;,
&lt;a href=&quot;https://wallabyjs.com/docs/features/selected-tests/&quot;&gt;selected or focused tests&lt;/a&gt;. This makes it easy
to concentrate on relevant parts of your project and avoid noise from unrelated or uncovered files.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Smart Start: Coverage shows only source files executed by the watched test files.&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;.only&lt;/code&gt; modifier: Coverage shows only source files executed by the selected tests.&lt;/li&gt;
  &lt;li&gt;Focused tests (via command, output icon, or test tree): Coverage shows only source files executed by the focused test(s).&lt;/li&gt;
&lt;/ul&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/vscode-cov-imp.gif&quot; /&gt;
&lt;/p&gt;
</description>
        <pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/coverage-improvements.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/coverage-improvements.html</guid>
        
      </item>
    
      <item>
        <title>Log Copying Improvements</title>
        <description>&lt;p&gt;Wallaby &lt;strong&gt;Logs&lt;/strong&gt; 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.&lt;/p&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/copy-log.png&quot; /&gt;
&lt;/p&gt;

&lt;p&gt;Users of Wallaby in JetBrains editors can also use this feature within Value Peek and Watch Expression hovers.&lt;/p&gt;

&lt;p&gt;This feature is also available in &lt;a href=&quot;https://quokkajs.com&quot;&gt;Quokka.js&lt;/a&gt;, our JavaScript playground.&lt;/p&gt;
</description>
        <pubDate>Thu, 14 Aug 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/copy-improvements.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/copy-improvements.html</guid>
        
      </item>
    
      <item>
        <title>VS Code Coverage Improvements</title>
        <description>&lt;p&gt;Wallaby for VS Code now shows &lt;strong&gt;file-level code coverage&lt;/strong&gt; directly in the &lt;strong&gt;Explorer View&lt;/strong&gt; and the &lt;strong&gt;Test Coverage View&lt;/strong&gt;. This makes it easier to spot what’s covered (and what isn’t) at a glance.&lt;/p&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/vscode-whatsnew-coverage.png&quot; /&gt;
&lt;/p&gt;

&lt;p&gt;By default, the file-level code coverage is displayed in the file explorer &lt;strong&gt;when Wallaby Coverage side view is
opened&lt;/strong&gt;. To always show the coverage in the Explorer View or completely disable coverage in the Explorer View, you may
use the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;wallaby.showCoverageInExplorer&lt;/code&gt; setting.&lt;/p&gt;

&lt;p&gt;These new features augment the existing Wallaby coverage features in the &lt;a href=&quot;https://wallabyjs.com/docs/intro/vs-code/#side-view&quot;&gt;Side View&lt;/a&gt;, providing a more integrated experience for managing test coverage.&lt;/p&gt;
</description>
        <pubDate>Thu, 31 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vscode-coverage.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vscode-coverage.html</guid>
        
      </item>
    
      <item>
        <title>Angular v20 support</title>
        <description>&lt;p&gt;Angular CLI v20 introduces a significant update: &lt;strong&gt;esbuild&lt;/strong&gt; is now the default build system, replacing &lt;strong&gt;webpack&lt;/strong&gt;. Wallaby now fully supports Angular CLI v20, enabling seamless testing for projects using either &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@angular/build:karma&lt;/code&gt; or legacy &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;@angular-devkit/build-angular:karma&lt;/code&gt; configurations.&lt;/p&gt;
</description>
        <pubDate>Fri, 25 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/angular-v20-support.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/angular-v20-support.html</guid>
        
      </item>
    
      <item>
        <title>Improved Side-by-Side and Compact Diffs for Jest/Vitest Asymmetric Matchers</title>
        <description>&lt;p&gt;Wallaby now renders cleaner, more readable diffs for Jest and Vitest tests using asymmetric matchers like &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;expect.any()&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;expect.objectContaining()&lt;/code&gt;, and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;expect.stringContaining()&lt;/code&gt;. Instead of showing verbose raw matcher code, Wallaby displays intuitive labels like &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Anything&amp;lt;String&amp;gt;&lt;/code&gt; or &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;StringContaining &quot;hello&quot;&lt;/code&gt; in &lt;strong&gt;side-by-side and compact views&lt;/strong&gt;, making it easier to spot what actually failed without losing access to full actual/expected values for copying or inspection.&lt;/p&gt;
</description>
        <pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/assymetric-matchers.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/assymetric-matchers.html</guid>
        
      </item>
    
      <item>
        <title>Automatic Node.js Version Selection Based on Project Configuration</title>
        <description>&lt;p&gt;Wallaby now automatically detects and selects the appropriate Node.js version for your project based on configuration files like &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;.nvmrc&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;.node-version&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;package.json (engines.node field)&lt;/code&gt;, 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. &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;nvm&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;volta&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;fnm&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;asdf&lt;/code&gt;, etc.). This eliminates the need for manual configuration and ensures your tests run in the correct Node.js environment without any additional setup.&lt;/p&gt;
</description>
        <pubDate>Mon, 30 Jun 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/auto-node-version.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/auto-node-version.html</guid>
        
      </item>
    
      <item>
        <title>Major Performance Improvements</title>
        <description>&lt;p&gt;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, &lt;strong&gt;use ~10x-12x less CPU and memory&lt;/strong&gt; for code insights, and avoid spawning unnecessary workers.&lt;/p&gt;
</description>
        <pubDate>Tue, 17 Jun 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/performance-june-25.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/performance-june-25.html</guid>
        
      </item>
    
      <item>
        <title>Support for Jest 30.0.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of &lt;a href=&quot;https://jestjs.io/blog/2025/06/04/jest-30&quot;&gt;Jest v30.0.x+&lt;/a&gt;. The recent
update of Jest included breaking changes that required updates to 
Wallaby’s Jest integration.&lt;/p&gt;
</description>
        <pubDate>Tue, 10 Jun 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jest-v30.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jest-v30.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v3.2.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v3.2.x+). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Tue, 03 Jun 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v3.2.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v3.2.html</guid>
        
      </item>
    
      <item>
        <title>Interactive Runtime Value Graphs</title>
        <description>&lt;p&gt;The new &lt;strong&gt;Interactive Runtime Value Graphs&lt;/strong&gt; feature lets you visualize runtime data as structured graphs directly in
your editor. It’s useful for inspecting deeply nested objects or large data sets that are hard to parse in raw text
form. The graph layout adapts well to various data shapes, and you can interactively &lt;strong&gt;collapse or expand&lt;/strong&gt; branches and
nodes to focus on the parts that matter. The graph &lt;strong&gt;updates automatically&lt;/strong&gt; as values change, giving you a live view of
your log’s state. &lt;a href=&quot;/blog/diagrams.html&quot;&gt;Read more in our blog&lt;/a&gt;.&lt;/p&gt;

&lt;p class=&quot;blog-image&quot;&gt;
  &lt;img src=&quot;/assets/img/vsc-diagram.gif&quot; /&gt;
&lt;/p&gt;
</description>
        <pubDate>Fri, 09 May 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/diagrams.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/diagrams.html</guid>
        
      </item>
    
      <item>
        <title>Copilot Agent tools and MCP support</title>
        <description>&lt;p&gt;Agentic AI workflows are transforming how developers interact with code, with &lt;strong&gt;context&lt;/strong&gt; playing a crucial role.
Wallaby’s new AI tools and &lt;strong&gt;MCP server&lt;/strong&gt; provide rich insights—such as &lt;strong&gt;runtime values, execution paths, and coverage
data&lt;/strong&gt;—to enhance agent capabilities. Now Wallaby enables &lt;strong&gt;Copilot Chat&lt;/strong&gt;, &lt;strong&gt;Cursor&lt;/strong&gt;, &lt;strong&gt;Claude Code&lt;/strong&gt;, &lt;strong&gt;Windsurf&lt;/strong&gt;, &lt;strong&gt;Cline&lt;/strong&gt;, and other agents to access detailed runtime context on demand.
&lt;a href=&quot;/blog/wallaby-mcp.html&quot;&gt;Read more in our blog&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Thu, 17 Apr 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/mcp.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/mcp.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v3.1.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v3.1.x+). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v3.1.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v3.1.html</guid>
        
      </item>
    
      <item>
        <title>Copilot Chat Integration</title>
        <description>&lt;p&gt;The best AI model for investigating unit test errors is the one with the most context — provided by the user and the
right tools. &lt;strong&gt;Wallaby now automatically provides GitHub Copilot with detailed context and tools&lt;/strong&gt; - including execution
paths, test coverage, and runtime values - to debug smarter. &lt;a href=&quot;/blog/wallaby-ai.html&quot;&gt;Read more in our blog&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Tue, 18 Feb 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/ai.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/ai.html</guid>
        
      </item>
    
      <item>
        <title>Keyboard Shortcuts</title>
        <description>&lt;p&gt;Wallaby UI now offers quick access to keyboard shortcuts documentation in the Overview and Side view panels, both inside
the editor and from the browser (when using &lt;a href=&quot;/blog/wallaby-2.html&quot;&gt;Linked or Standalone Mode&lt;/a&gt;). Press the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;?&lt;/code&gt; key while
focused on either panel, or click the keyboard icon on the right side of the Overview panel, to display a comprehensive
list of available shortcuts.&lt;/p&gt;
</description>
        <pubDate>Wed, 12 Feb 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/kbd-shortcuts.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/kbd-shortcuts.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v3.0.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v3.0.x+). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Thu, 23 Jan 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v3.0.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v3.0.html</guid>
        
      </item>
    
      <item>
        <title>Value Peek</title>
        <description>&lt;p&gt;Wallaby for VS Code and JetBrains editors now supports &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Value Peek&lt;/code&gt;, a way to quickly see any value just by hovering over it. Wallaby will handle execution of the relevant tests to provide values, which will be displayed in the hover. To keep your editor clutter-free, values shown this way will not appear next to your code by default (but can be made to appear using the “Explore Value” action available in the hover). Value Peek can be toggled on or off to fit with your workflow.&lt;/p&gt;
</description>
        <pubDate>Tue, 21 Jan 2025 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/value-peek.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/value-peek.html</guid>
        
      </item>
    
      <item>
        <title>Introducing Wallaby v2</title>
        <description>&lt;p&gt;We’ve re-imagined Wallaby.js to deliver more power, flexibility, and a seamless experience across all editors. Wallaby v2 introduces an all-new UI, enhanced debugging tools like the Interactive Time Travel Debugger, and advanced test execution monitoring. With Linked and Standalone modes, it supports any editor, making it easier than ever to streamline your workflow. &lt;a href=&quot;/blog/wallaby-2.html&quot;&gt;Read more in our blog&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Thu, 17 Oct 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/wallaby-v2.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/wallaby-v2.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v2.1.0+</title>
        <description>&lt;p&gt;Wallaby has been updated to support the latest version of vitest, v2.1.0. This update 
was necessary due to breaking changes introduced in the latest vitest 
release.&lt;/p&gt;
</description>
        <pubDate>Fri, 13 Sep 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v2.1.0.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v2.1.0.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v2.0.5+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v2.0.5). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Thu, 01 Aug 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v2.0.5.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v2.0.5.html</guid>
        
      </item>
    
      <item>
        <title>Experimental node:test support</title>
        <description>&lt;p&gt;Wallaby now provides experimental support for the node native testing module, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;node:test&lt;/code&gt; (detailed in 
&lt;a href=&quot;/docs/integration/node-test.html&quot;&gt;our docs&lt;/a&gt;). You can now use Wallaby with projects that use &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;node:test&lt;/code&gt;, starting 
from Node v22.3.0 or higher. As this is an experimental feature, we anticipate there might be edge cases or unique 
configurations that could cause issues. We encourage you to 
&lt;a href=&quot;https://github.com/wallabyjs/public/issues/new&quot;&gt;report any issues or provide feedback&lt;/a&gt; so we can improve this 
integration.&lt;/p&gt;
</description>
        <pubDate>Wed, 17 Jul 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/node-test-integration.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/node-test-integration.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v2.0.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v2.0.0). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Tue, 09 Jul 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v2.0.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v2.0.html</guid>
        
      </item>
    
      <item>
        <title>JetBrains Previous / Next Error</title>
        <description>&lt;p&gt;Wallaby for JetBrains editors provides two additional actions, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Go to Next Error&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Go to Previous Error&lt;/code&gt;, allowing you to quickly navigate between errors in your tests. This same functionality was already available in VS Code with the VS Code built-in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Go to Next Problem&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Go to Previous Problem&lt;/code&gt; actions.&lt;/p&gt;
</description>
        <pubDate>Mon, 08 Jul 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jb-prev-next-error.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jb-prev-next-error.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v1.6.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v1.6.0). The recent
update of vitest included breaking changes that required updates to 
Wallaby’s vitest integration.&lt;/p&gt;
</description>
        <pubDate>Tue, 07 May 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v1.6.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v1.6.html</guid>
        
      </item>
    
      <item>
        <title>Jest v30 (Alpha 3) Support</title>
        <description>&lt;p&gt;The latest version of Jest (v30.0.0-alpha.3) is now supported by Wallaby. This version included a number of breaking changes that required updates to Wallaby’s Jest integration.&lt;/p&gt;
</description>
        <pubDate>Sat, 20 Apr 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jest-30-alpha-3.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jest-30-alpha-3.html</guid>
        
      </item>
    
      <item>
        <title>Jest Performance Improvements</title>
        <description>&lt;p&gt;The latest version of Wallaby significant improves performance startup and test execution times for Jest projects; Jest’s TypeScript configuration files are now transpiled using &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;swc&lt;/code&gt; instead of &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;ts-node&lt;/code&gt;, and large mono-repos only load project configuration on demand. For large projects, test execution times can be up to 90% faster than before.&lt;/p&gt;
</description>
        <pubDate>Fri, 12 Apr 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jest-perf-improvements.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jest-perf-improvements.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v1.4.x+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v1.4.0). The recent
update of vitest included breaking changes that required rework of 
Wallaby’s integration.&lt;/p&gt;
</description>
        <pubDate>Mon, 18 Mar 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v1.4.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v1.4.html</guid>
        
      </item>
    
      <item>
        <title>Support for AVA 6.1.2+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of AVA (v6.1.2). The recent
version included breaking changes that required rework of 
Wallaby’s integration.&lt;/p&gt;
</description>
        <pubDate>Fri, 01 Mar 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/ava-6.1.2.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/ava-6.1.2.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v1.3.1+</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of vitest (v1.3.1). The recent
update of vitest included breaking changes that required rework of 
Wallaby’s integration.&lt;/p&gt;
</description>
        <pubDate>Fri, 23 Feb 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v1.3.1.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v1.3.1.html</guid>
        
      </item>
    
      <item>
        <title>Support for Import Assertions and Attributes</title>
        <description>&lt;p&gt;Wallaby now supports Import Attributes, a new JavaScript language feature. Import Attributes replaced the Import Assertions language feature, which was already supported by Wallaby. Wallaby now supports both of these language features.&lt;/p&gt;
</description>
        <pubDate>Fri, 16 Feb 2024 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/import-features.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/import-features.html</guid>
        
      </item>
    
      <item>
        <title>Support for Vitest v1.x</title>
        <description>&lt;p&gt;Wallaby now supports &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;vitest@v1.0.x&lt;/code&gt;, a major update that was just released yesterday. We had been closely monitoring the progress of Vitest’s 1.0.x beta releases to ensure we could support the official &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;1.0.x&lt;/code&gt; version as soon as possible after it was released. There were numerous breaking changes and enhancements introduced in Vitest’s latest version that required updates to Wallaby’s integration. If you are using an earlier version of Vitest, we recommend reading the &lt;a href=&quot;https://vitest.dev/guide/migration.html#migrating-from-vitest-0-34-6&quot;&gt;Vitest migration guide&lt;/a&gt; to understand changes that may affect your project.&lt;/p&gt;
</description>
        <pubDate>Wed, 06 Dec 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/vitest-v1.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/vitest-v1.html</guid>
        
      </item>
    
      <item>
        <title>Jasmine v5.1.x</title>
        <description>&lt;p&gt;Wallaby now supports the latest version of Jasmine (v5.1.1) for both &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;node.js&lt;/code&gt; and &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;browser&lt;/code&gt; tests. The latest version of Jasmine included breaking changes that required updates to Wallaby’s integration. To use the latest version of Jasmine, please ensure you’re running the latest version of Wallaby.&lt;/p&gt;
</description>
        <pubDate>Tue, 14 Nov 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jasmine-v5.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jasmine-v5.html</guid>
        
      </item>
    
      <item>
        <title>Node.js 21.x Support</title>
        <description>&lt;p&gt;Wallaby now supports node.js v21.x. The recent update of node included a number of breaking changes to projects and tools that use ES Modules.&lt;/p&gt;
</description>
        <pubDate>Thu, 09 Nov 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/node-21.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/node-21.html</guid>
        
      </item>
    
      <item>
        <title>NX v17.x Support</title>
        <description>&lt;p&gt;Wallaby has been updated to support NX v17.x. This new version included breaking changes to internal APIs for loading NX configuration.&lt;/p&gt;
</description>
        <pubDate>Tue, 31 Oct 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/nx-17.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/nx-17.html</guid>
        
      </item>
    
      <item>
        <title>Logpoints for JetBrains IDEs</title>
        <description>&lt;p&gt;Wallaby for JetBrains editors now supports &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Logpoints&lt;/code&gt;, allowing you to use breakpoints to log values.
Logpoints allow you to display the value of any expression without modifying your code, simply by placing a breakpoint next to the expression you want to log.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Quickly log values:&lt;/strong&gt; Simply place a 🔴 breakpoint on a line (&lt;span class=&quot;code-text font-bold highlighted-text&quot;&gt;F9&lt;/span&gt;) to log its value.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;No debugger required:&lt;/strong&gt; Logpoints require zero setup / configuration and work seamlessly using Wallaby’s existing runtime.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Effortless management:&lt;/strong&gt; No need to modify your source code; Logpoints can be added/removed with existing keyboard shortcuts.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Seamless editor integration:&lt;/strong&gt; Logpoints persist when files are closed and reopened, and are managed by IntelliJ.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Clear visual indicators:&lt;/strong&gt; Easily see and understand what’s being logged.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Works on classes and functions:&lt;/strong&gt; Quickly see logs for all lines within a class or function by adding a logpoint to the declaration.&lt;/li&gt;
&lt;/ul&gt;

&lt;p class=&quot;blog-image&quot;&gt;&lt;img src=&quot;/assets/img/jb-logpoints.gif&quot; /&gt;&lt;/p&gt;

&lt;p&gt;The Logpoints feature was inspired by similar functionality in our other product, &lt;a href=&quot;https://console-ninja.com/&quot;&gt;Console Ninja&lt;/a&gt;;
if you haven’t already tried Console Ninja, it’s worth checking out.&lt;/p&gt;
</description>
        <pubDate>Thu, 05 Oct 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/jb-logpoints.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/jb-logpoints.html</guid>
        
      </item>
    
      <item>
        <title>Logpoints for VS Code</title>
        <description>&lt;p&gt;Wallaby for VS Code now supports &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Logpoints&lt;/code&gt;, allowing you to use breakpoints to log values.
Logpoints allow you to display the value of any expression without modifying your code, simply by placing a breakpoint next to the expression you want to log.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Quickly log values:&lt;/strong&gt; Simply place a 🔴 breakpoint on a line
(&lt;span class=&quot;code-text font-bold highlighted-text&quot;&gt;F9&lt;/span&gt;) or next to an expression (&lt;span class=&quot;code-text font-bold highlighted-text&quot;&gt;⇧ F9&lt;/span&gt;) to log its value.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;No debugger required:&lt;/strong&gt; Logpoints require zero setup / configuration and work seamlessly using Wallaby’s existing runtime.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Effortless management:&lt;/strong&gt; No need to modify your source code; Logpoints can be added/removed with existing keyboard shortcuts.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Seamless integration with VS Code:&lt;/strong&gt; Logpoints persist when files are closed and reopened, and are managed by VS Code.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Clear visual indicators:&lt;/strong&gt; Easily see and understand what’s being logged, especially when using inline breakpoints.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Works on classes and functions:&lt;/strong&gt; Quickly see logs for all lines within a class or function by adding a logpoint to the declaration.&lt;/li&gt;
&lt;/ul&gt;

&lt;p class=&quot;blog-image&quot;&gt;&lt;img src=&quot;/assets/img/vsc-logpoints.gif&quot; /&gt;&lt;/p&gt;

&lt;p&gt;The Logpoints feature was inspired by similar functionality in our other product, &lt;a href=&quot;https://console-ninja.com/&quot;&gt;Console Ninja&lt;/a&gt;;
if you haven’t already tried Console Ninja, it’s worth checking out.&lt;/p&gt;
</description>
        <pubDate>Thu, 21 Sep 2023 00:00:00 +0000</pubDate>
        <link>https://wallabyjs.com/whatsnew/logpoints.html</link>
        <guid isPermaLink="true">https://wallabyjs.com/whatsnew/logpoints.html</guid>
        
      </item>
    
  </channel>
</rss>
