Turbo Console Log v3.8.0 addresses the two most frequent themes from our recent survey and support reports: performance bottlenecks and log noise management. We removed the TypeScript compiler layer that was adding activation overhead and slowing work in large files—especially on lower-spec machines—and introduced the new Hide Logs feature in Turbo Pro so you can suppress repetitive or low-value output directly in the panel.

We kept the architecture and swapped the TypeScript compiler-based AST stage for the lighter Acorn parser—retaining insertion accuracy while reducing package size, bundle weight, activation time, and ongoing CPU/memory usage.

The TypeScript AST engine in v3.3.0 improved accuracy in log placement and context analysis, but the compiler layer added overhead across multiple areas: slower activation, reduced responsiveness in large files, and higher CPU usage on lower-spec machines.

The TypeScript dependency made the extension heavy. 2.6MB VSIX package. 3.7MB bundle size. Load time of 860ms that could stall VS Code startup on some setups, especially on lower-spec machines or when working with large codebases.

Rather than compromise on accuracy, we switched to a lighter AST parser that delivers the same insertion accuracy with dramatically better performance.

We replaced TypeScript's parser with Acorn — a lightweight JavaScript parser that delivers the same code analysis accuracy with significantly better performance characteristics.

96% smaller package (from 2.6MB to 108KB). 85% smaller bundle (from 3.7MB to 560KB). 89% faster startup (from 860ms to 96ms).

The Acorn parser uses significantly less CPU and memory compared to TypeScript's compiler. This reduces the extension's impact on VS Code performance and system resources.

Since Turbo Pro is built on the same core engine, all performance improvements apply to Pro users. The Pro panel loads faster and uses fewer system resources.

All existing Pro features now run with the improved performance characteristics.

In workspaces with multiple folders, the PRO Panel could appear empty or partial. v3.8.0 fixes this—files across all workspace roots are now detected, displayed, and kept in sync.

Based on user feedback, we've added the ability to selectively hide console logs in the Turbo Pro panel. This addresses the most requested feature from our user community.

When debugging complex applications, you often need to filter out irrelevant logs to focus on specific issues. The hide logs feature gives you precise control over which logs are visible in your panel.

The feature offers multiple ways to filter logs: manual hiding for quick cleanup, or rule-based filtering for automated log management.

Debugging a complex React component? Hide prop-validation noise to focus on state changes. Inspecting an API flow? Hide UI logs to see only network activity. Tracing performance issues? Hide everything except timing logs.

Your panel stays clean, fast, and exactly as focused as you need it to be.

This release required a complete rewrite of the core parsing engine. We maintained backward compatibility while switching from TypeScript's compiler to Acorn, ensuring existing functionality works seamlessly.

Turbo Console Log v3.8.0 combines improved performance with enhanced functionality. The new engine processes code faster while the hide logs feature gives you better control over your debugging workflow.

Turbo Console Log v3.8.0 delivers measurable performance improvements and adds the most requested Pro feature. VS Code starts faster, log insertion is more responsive, and Pro users get better log management tools.

The update maintains full backward compatibility while significantly improving the extension's performance profile.