10,000 Times Cleaner Code Just By Using This Tool.

Ayush Niroula — Wed, 25 Sep 2024 03:45:58 +0000

Ever stared at your codebase thinking, “Wow, that’s a lot of console.log clutter!"? Or maybe you’ve spent way too much time hunting down those rogue print statements you used while debugging. Well, good news—Eradicate (era) is here to rescue you from that mess! 🦸‍♀️

Era is a slick open-source tool that automatically cleans your codebase, wiping out unwanted logs, prints, and debugging statements across multiple languages. No more manual code cleanup or dealing with bloated files filled with leftover logs. It’s like Marie Kondo for your code! ✨

In this story, I’m going to show you how era works, why it’s a game-changer, and how you can get started ASAP.

🎯 Why Era? Because Nobody Has Time to Manually Clean Code! ⏳
Picture this: You’re deep in the middle of a project, dropping console.log and print() statements left and right to debug your code. By the time you finish, you’ve got a sea of logs floating around your files, making it hard to see the real logic.

Enter Eradicate (era). It’s like having a digital cleaning assistant that sweeps through your codebase, finds those pesky outputs, and wipes them out faster than you can say “refactor.” Whether you’re working on a personal project or contributing to a large team, era automates the boring cleanup part, so you can focus on the fun stuff — like, you know, actually coding. 😎

⚡️ Key Features You’ll Love
Multi-language support: Clean up logs in JavaScript, Python, PHP, Go, Ruby, and more. No matter the language, era has your back. 💻
Customizable Config: You decide what gets cleaned and what stays — because not all logs deserve the boot.
Target Specific Files/Folders: Just finished working on a feature? Run era on a single file or folder. Easy peasy.
Ignore What Matters: Don’t want to clean certain files or directories (like node_modules)? Era makes it simple to exclude what you don’t want to touch.
🚀 How to Get Started with Era
Ready to clean up your code like a boss? Here’s your step-by-step guide.

Initialize Era in Your Project First things first — you need to let era know where to get started. Run the following command to initialize era in your project:

era init

This creates a shiny new erd.yaml config file in your root directory. It’s your personalized cleanup map where you define exactly what needs scrubbing.

Clean Up Logs and Prints Like a Pro Time to make your code spotless! Run the clean command, and era will scan your project and clean out all those pesky logs:

era clean

By default, era will check your erd.yaml file for cleaning rules. If it doesn’t find one, no worries—it’s got default settings ready to go. 🧼✨

Target a Specific File or Folder Don’t need to clean the whole project? No problem. You can target individual files or folders:

To clean a specific file:

era remove -f path/to/yourfile.js

Or to clean a whole folder:

era remove -d path/to/yourfolderEra will carefully check the file or folder, hunt down the unwanted logs, and leave the rest untouched. 🕵️‍♀️

🔧 The Magic Behind Era’s Config File
Let’s talk about the secret sauce: the erd.yaml configuration file. Here’s a breakdown of what it does and how you can tweak it to fit your project like a glove:yml

Root: "."
ReportPath: "era-reports"
IgnoreKeyword:
  - "erd:ignore"
  - "erd:ignoreAll"
IgnoreFileExtensions:
  - ".exe"
  - ".dll"
  - ".zip"
  - ".tar"
IgnoreDirs:
  - "node_modules"
  - ".git"
  - "vendor"
IgnoreFiles: []
ListenType: "command"

Root: This is where era starts its search — usually your project’s root directory.
ReportPath: After each run, era will generate a report in this directory, so you can see exactly what was cleaned. 📊
IgnoreKeyword: Add custom tags to your code like erd:ignore to stop era from cleaning certain sections.
IgnoreFileExtensions: These are the file types era won’t touch — think binaries or compressed files.
IgnoreDirs: Directories like node_modules or .git are automatically excluded to save you time. No one needs to clean those, right? 😅
ListenType: Currently, this is set to “command,” meaning era listens for cleanup commands from you. More listen types may come in the future — stay tuned!
🎉 The Best Part: It’s Free and Open-Source!
Yup, you heard that right. Eradicate (era) is open-source, meaning you can use it, modify it, and even contribute back to it! It’s all about helping fellow developers keep their codebases clean without the hassle.

💡 Final Thoughts
Eradicate isn’t just a tool — it’s a timesaver, a productivity booster, and a clutter-buster. Whether you’re working solo or part of a larger team, using era helps you maintain a tidy codebase with minimal effort.

If you’re tired of manually cleaning up your files, give era a spin. It’s free, easy to set up, and — trust me — it’ll save you hours of time.

Join the revolution! 🚀 You can find the code on Github and contribute to making this tool even better.

Happy Coding! 💻✨

Eradicate (era): A Powerful Open-Source Tool for Code Cleanup

Ayush Niroula — Tue, 24 Sep 2024 01:12:56 +0000

Thrilled to announce my open-source project Eradicate (era) 🎉 era is a versatile tool that simplifies cleaning and transforming codebases across multiple languages. From removing unwanted logs to customizing file cleanup, era helps developers maintain cleaner and more efficient projects.

Check it out, give it a try, and contribute to making development a little bit easier for everyone! 🌟

https://github.com/wadmit/era

DEV Community: Ayush Niroula

10,000 Times Cleaner Code Just By Using This Tool.

Eradicate (era): A Powerful Open-Source Tool for Code Cleanup