v3.1.0: Turbo PRO v2 β Faster, Smarter, Stronger β‘
Turbo PRO v2 Benchmark: Real-World Performance
How Turbo PRO v2 Works: Technical Overview
Debugging with Memory: Why Turbo PRO Panel Matters!
v3.0.0: Turbo PRO Officially Launches β A New Era of Debugging Begins π
v2.18.0: Thank You for the Surge β Letβs Clear the PRO Access Confusion π«
Turbo Console Log v2.17.0: PRO Enters the Arena π§¨
Turbo Console Log v2.16.0: The Stage Is Set For Something Big β‘οΈ
Turbo Console Log v2.15.0: A New Chapter Begins
Turbo Console Log v2.14.0: More Stable, Sharper, and Ready for What's Next
Debugging Between Science and Art
Turbo Console Log v2.13.0: More Stable and Flourishing thanks to You!
Turbo Console Log v2.12.0: More Stable, But an Uncertain Future!
Turbo Console Log v2.11.0: A Step Forward in Debugging
Empowering Turbo Console Log: Why Your Support Matters
Turbo Console Log 2025: A Clear Path to Consistency and Growth
Introducing the New Turbo Console Log Website
The Motivation Behind Turbo Console Log
How Turbo PRO v2 Works: Technical Overview
Publication Date: 25/06/2025
Author: Anas Chakroun

4-6 minutes

Performance First: What Changed in v2
One of the most demanding operations in Turbo PRO is the initial construction of the logs tree, which involves recursively scanning your entire workspace to find and register every Turbo log.
On large workspaces, this operation is anything but trivial. While the first version did exclude obvious heavy folders like `node_modules`, we were still walking through nearly every other directory β even ones that should've been ignored. This made the panel feel sluggish on complex repos.
Smarter Tree Construction
In Turbo PRO v2, we now respect the .gitignore file recursively β just like Git does β which means all ignored files and folders are skipped entirely during tree creation. This dramatically reduces unnecessary checks and speeds up the entire scan.
And because the tree-building process is naturally recursive, we made it parallel. Each subtree is processed in isolation using worker concurrency β paving the way for the upcoming 'proPanelTreeConcurrency' setting to allow power users to scale this even further.
Turbo VDOM: Fast Syncs by Design
Once the tree is constructed, we don't rebuild it entirely every time something changes. Turbo PRO v2 introduces a Virtual DOM engine β Turbo VDOM β designed specifically for incremental updates to the logs tree.
This means that when something changes in your workspace, only the affected parts of the tree are recalculated and re-rendered. The result is blazing fast syncs and a smoother user experience β especially in real-time editing sessions.
Stronger Detection Engine
In Turbo PRO v1, some developers encountered false positives β lines being marked as logs when they weren't, or real logs being skipped.
With v2, we dramatically improved the detection engine by tightening and expanding our internal regex strategy. From day one, Turbo has relied on regex β not heavy ASTs β because it's lighter, faster, and easier to evolve.
This release refines that original vision. We've enhanced our pattern recognition logic to handle edge cases with higher precision while keeping detection blazing fast across massive JS/TS codebases.
Real World Benchmark
Curious how fast Turbo PRO v2 really is? Explore the benchmark results across massive projects like React, Storybook, and Vite.
Conclusion
Turbo PRO v2 isn't just more powerful β it's smarter, faster, and built on a foundation designed to scale. If v1 was the concept, v2 is the real engine. And it's only going to get better from here.
Big thanks to all early adopters who pushed us to make this happen. You helped us turn performance into a priority β and it shows.