Turbo Console Log has always relied on regex to power its smart detection engine. It’s fast, lightweight, and does a great job analyzing local lines of code. But when it comes to deeply nested code, multiline ternaries, or complex formatting, regex starts to fall short.

That’s why v3.2.0 introduces AST (Abstract Syntax Tree) parsing. While AST adds some internal complexity, it unlocks compiler-level precision — allowing Turbo to understand the full scope of variables, not just the visible line. We’ve now migrated the logic for ternary expressions and function parameters to AST.

This is just the beginning. The goal is to slowly move all critical checkers and line deduction helpers over to AST, especially for areas that regex consistently struggles with. But regex isn’t going away — it will still be used where it makes sense.

Alongside this milestone, v3.2.0 also ships key bug fixes to handle advanced object literal assignments with type annotations and edge cases in default settings — all based on real feedback from the community.

Since launching Turbo PRO v2, feedback has been strong — fast activations, stable performance across big projects, and only a handful of minor edge cases that were quickly handled.

If you're enjoying the free version and want to take it further — now's the perfect time to unlock PRO. Lifetime license, 5 activations per version, and premium stability built for devs who demand more.

The AST refactor will continue across other log detection cases: destructured objects, nested assignments, spreads, etc. The long-term goal? Zero guesswork and logs that feel native to the code they land in.

If you hit weird cases, want to share your codebase edge cases, or have feature ideas — hit us up. You’re shaping the future of Turbo Console Log.