| Crates.io | cargo-recursive-clean |
| lib.rs | cargo-recursive-clean |
| version | 0.2.310 |
| created_at | 2023-04-09 22:09:47.203819+00 |
| updated_at | 2024-01-06 20:15:05.638615+00 |
| description | A CLI app that cleans all Rust projects recursively given a base directory. |
| homepage | |
| repository | https://github.com/OLoKo64/cargo-recursive-clean |
| max_upload_size | |
| id | 834559 |
| size | 34,688 |
A CLI app that cleans all Rust projects recursively given a base directory.
cargo install cargo-recursive-clean
To clean all Rust projects recursively in the current directory:
cargo-recursive-clean
You can also use the extending cargo feature:
cargo recursive-clean
All the option below are also available with this feature.
To clean all Rust projects recursively in a specific directory:
cargo-recursive-clean <path-to-directory>
You can also specify to only clean release or doc artifacts:
cargo-recursive-clean --release
cargo-recursive-clean --doc
You can also specify to only print the directories that would be cleaned, without actually cleaning them:
cargo-recursive-clean --dry
You can specify a list of patterns to ignore when cleaning. This is useful if you have a project that you don't want to clean, or if you have a project that you want to clean but it's not a Rust project. By default, the following patterns are ignored: '**/node_modules/**','**/target/**'.
You can also specify a list of patterns to ignore when cleaning, for example:
cargo-recursive-clean --ignored-patterns '**/node_modules/**,**/venv/**'
This will ignore all node_modules and venv directories.
To not ignore any patterns, you can simply pass an empty string:
cargo-recursive-clean --ignored-patterns ''
This project is licensed under the MIT License - see the LICENSE file for details.