This depends specifically on your Ruby version manager. Then when you are confident, you can remove the “dryrun” param and run it for real. If you’re worried, you can see the results first with “dryrun”. Ruby DevelopersĬlean up old versions of Gems with the cleanup command.
Using asdf? List your installed versions with asdf list nodejs and then remove any with asdf uninstall nodejs. Using nvm? List your installed versions with nvm ls and then remove any with nvm uninstall. Using n? List all versions of node + your installed ones with n ls and then remove any with n rm. Consult uninstall for your specific version manager. This varies depending on your Node manager. name "node_modules" -type d | xargs rm -rf Remove old versions of Node If you’re feeling quite aggressive, you can just clear out ALL node_modules folders and re-install as needed, by removing the mtime flag. name "node_modules" -type d -mtime +120 | xargs rm -rf Removes all node_modules folders older than 4 months: find. This does mean you will have to npm i or yarn again in those older projects. The following command finds all node_modules folders older than 120 days and removes them. done JavaScript Developers Delete OLD `node_modules` embedded in projects
#App mac os cleaner code
This code will CD into all folders in the current working directory, and then run the command to clean merged branches for each! for d in */ do cd $d echo WORKING ON $d git branch -merged master | grep -v "\* master" | xargs -n 1 git branch -d cd. WOW, what a mouthful for only one project! Let’s make it worse. You can remove all the merged branches from a single project with this command: git branch -merged master | grep -v "\* master" | xargs -n 1 git branch -d Git is great, but it’s not hard to leave a bunch of merged branches laying around on your local machine! Those branches aren’t useful anymore, and sometimes make naming conflicts for future branches. So you can run brew doctor and get some additional chores you could take care of to have it run properly. Cleanup handles this for you! General Brew Maintenanceīrew is a complicated system, and no one knows it better than the maintainers. You might have used brew prune in the past, but that has been deprecated.
#App mac os cleaner update
Update then remove old formulae and their folders: brew update & brew upgrade & brew cleanup Update, upgrade, and then clean up those files you’re not going to use. This one usually shaves off hundreds of megs of data. Mine is reporting 132.2 GB before cleaning.
#App mac os cleaner how to
But once a year, developers should run through a few manual commands, because auto-cleaners won’t know how to take care of a developer machine.īefore we start, let’s look at how much “Free Space” you’re starting with: Sure, for general maintenance, nothing beats CleanMyMac. But it never cleans a development machine as I can. I love cleaning software? PLZ! Remove duplicates, find old OS cruft etc. Clean up your dev environment you filthy animal!
0 kommentar(er)
