Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Nonsole LogsNew to Visual Studio Code? Get it now.
Nonsole Logs

Nonsole Logs

Christian Konnaris

|
4 installs
| (0) | Free
Smartly remove all console logs in the current file.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Console.log Remover

An intelligent VS Code extension that goes beyond simple text searching to safely and surgically remove console.log statements from your codebase using AST (Abstract Syntax Tree) parsing.

🚀 Why this is better than Search & Replace

After a long debugging sessions, often want to remove our left behind console.log statements. This takes effort, and often leads to broken code on the go, if you accidentally delete something that you did not want. This extension parses your code to understand its structure, offering several advantages:

  1. Context Awareness: It won't touch console.log strings inside your comments, string literals, or template strings.
  2. Syntax Safety: It understands the boundaries of expressions. It won't accidentally delete too much of a line.
  3. Smart Preservation: It can identify nested function calls inside a log and keep them while removing the log itself.
  4. Language Support: Built-in support for TypeScript, JSX, and TSX out of the box.

✨ Key Features

  • Deep Cleaning: Removes single-line and multi-line console.log statements.
  • Smart Removal: If you have logic inside your logs (like a function call that performs a side effect), the extension keeps the function call but removes the wrapper.
  • Arrow Function Support: Correctly handles logs inside expression-bodied arrow functions.
  • Safety First: Specifically avoids modifying code inside comments or strings.

📖 Examples

Smart Removal (Preserving Logic)

Standard tools would delete the entire line, potentially breaking your logic if the function inside the log was necessary. This extension extracts the inner call and keeps it there:

Before:

console.log(initializeAnalytics(), fetchData(id));

After:

initializeAnalytics(), fetchData(id);

Nested Console Logs

If you accidentally nested logs, it cleans them up recursively. Before:

console.log(console.log("Deep log"));

After: (Entirely removed)

Safety with Comments and Strings

Before:

// console.log("I am a comment");
const msg = "Don't delete this console.log(123)";
console.log("Delete me");

After:

// console.log("I am a comment");
const msg = "Don't delete this console.log(123)";

Arrow Functions

Before:

const logData = (data) => console.log(data);

After:

const logData = (data) => ;

Console.log as a Value

When console.log is used as a value (like passing it as an argument), the extension safely removes it without breaking the syntax.

Before:

event.register(console.log);

After:

event.register();

Console.log as a

🛠 Usage

  1. Open the file you want to clean.
  2. Open the Command Palette (Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux).
  3. Type Remove console logs in current file and hit enter.

⚙️ Requirements

  • Visual Studio Code v1.107.0 or higher.

📝 Known Issues

  • Currently focuses strictly on console.log. Others functions like console.error, console.warn are ignored, as we assume they are placed on purpose.
  • Sequence expressions will leave trailing commas behind. Removing them is error prone so not implemented. It's anyways a practice that should be avoided.

Before

console.log(123),console.log(456);

After

, ;
  • Console logs used as values inside string templates will not be removed. As this is also not recommended behaviour in the first place and would need a specific implementation. e.g.
const mystr = `Hello, ${console.log(user)}!`

⚖️ License

MIT © Christian Konnaris

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft