Question 1

How to use Kondo to clean only old Node.js projects?

Accepted Answer

Use the CLI with the --older flag, e.g., 'kondo --older 3M', to target projects modified more than 3 months ago. This works for Node.js and other supported types based on last modified timestamps.

Question 2

Kondo vs npkill: which is better for cleaning node_modules?

Accepted Answer

Kondo supports multiple languages and has a GUI, making it better for mixed environments. Npkill is Node.js-specific and may be simpler for pure JavaScript projects; choose based on your language diversity needs.

Question 3

Does Kondo clean Python virtual environments?

Accepted Answer

Yes, Kondo supports Python projects and can clean virtual environment folders if detected as part of the project structure, as indicated in the supported types list in the README.

Question 4

How to exclude certain directories from Kondo cleanup?

Accepted Answer

Kondo does not have a built-in exclusion feature; you need to manually avoid running it on those directories or use filesystem permissions, as it focuses on automatic detection of standard artifacts.

Question 5

Is Kondo safe to run on a server with production code?

Accepted Answer

It includes safety prompts, but since it performs irreversible deletions, use with extreme caution. Always have backups and test in non-production environments first to avoid critical data loss.

Question 6

Can Kondo clean build artifacts from Docker projects?

Accepted Answer

Kondo does not explicitly list Docker support; it targets language-specific dependency folders, so Docker caches or volumes might not be covered, requiring manual cleanup or other tools.

Kondo

What is Kondo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions