v3.25.0: Never Commit a Debug Log Again 🧹
Publication Date: 24/06/2026
Author: Anas Chakroun
5-6 minutes
Auto-cleanup on commit is live in Turbo Pro v3.25.0. You insert debug logs to move fast — and then you have to remember to strip every one of them before it reaches a commit. That tax is gone. From this release, Turbo Pro removes the debug logs you added automatically, the moment you commit.
Every other tool in this space only detects the problem. Linters warn you. Pre-commit hooks fail your commit and hand the work back. You still open the files and delete the logs yourself. Turbo does the deletion for you — scoped to the lines you changed and driven by a cleanup config you control.
What happens when you commit
You debug the way you always do — spray console.logs across a few files, fix the bug, and reach for git commit. Turbo catches that moment. Before the commit goes through, it finds the logs that match your cleanup config in your staged changes and removes them for you.
You stay in control the whole time. Turbo shows you exactly what it is about to remove — logs found in your staged files — and you choose: Remove & Commit to clear them and commit clean, or Commit Anyway to keep them this once. Commit from the terminal instead of the editor? An optional pre-commit hook brings the same behavior to git commit on the command line.
Live Cleanup Preview
Right inside the Log Cleanup panel, the Auto-Cleanup Preview lists every log queued for removal, grouped by file, so there are never surprises in your diff. It distinguishes the logs that are staged (and will be removed on commit) from ones that are still pending because the change isn't staged yet. Click any entry to jump straight to its line and eyeball it before you commit.
You decide what gets removed
Auto-modifying code at commit time only works if you stay in control, so auto-cleanup never guesses. It removes exactly what your Log Cleanup config matches, scoped to the lines you actually changed, and it shows you the full list before anything happens.
What gets removed is up to you
- Flags every log by default — narrow it any time. Out of the box, auto-cleanup targets every debug log in your changed lines (
console.log,console.error,print,error_log, and so on), so it works the moment you enable it. Want it tighter? Check the specific functions you care about in the Log Cleanup config and they become the allow-list — only those get removed. - Want only your Turbo logs gone? Turn on 🚀 Turbo Logs Only. With it on, cleanup limits itself to logs Turbo inserted and leaves your hand-written logging untouched. Leave it off and cleanup treats every matching log the same — Turbo or manual — so set it to match how you work.
- Scoped to your current changes. It only ever looks at the changed lines in your staged files — never the rest of the file or the wider workspace — and skips files with unstaged or unsaved changes so it can't commit work you didn't mean to.
- Always previewed, never silent. The Auto-Cleanup Preview lists every line the config matched, and nothing is removed until you choose Remove & Commit.
Turn it on
If you already run Turbo Pro, you're seconds away:
- Open the Log Cleanup panel in the Turbo sidebar.
- Make sure 🧹 Auto-cleanup on Commit is enabled (it is, by default).
- Optionally narrow the scope in the same panel: check specific log functions to limit cleanup to just those, and turn on 🚀 Turbo Logs Only if you want to leave your hand-written logging untouched.
- Committing from the terminal? Run
Turbo Console Log Pro: Install Pre-commit Hookfrom the Command Palette. - Commit as you normally would — and never strip a debug log by hand again.
Not a subscription. One-time purchase, lifetime access — no recurring charges. Buy it once and every future release is yours.