As you may know, Meteor stores downloaded Atmosphere packages in a cache in your user directory (~/.meteor/packages). However, the longer you use Meteor, the more packages and package updates are downloaded and the larger this cache will get because Meteor doesn’t remove old or unused packages (yet). There is a request for this feature but until it’s implemented in the Meteor tool, you can use my meteor-cleaner npm package to remove unused packages and free up (a lot of) disk space!
After installing it with meteor npm install -g meteor-cleaner, clean-package-cache can be used like a built-in Meteor command:
meteor clean-package-cache [options]
Windows is currently not supported!
See the package README.md for details and an explanation of the options.
The advantange of clean-package-cache over just removing ~/.meteor/packages is that you have more control over which packages are removed. For example, you can run meteor clean-package-cache --keep-scanned ~/Projects to scan all Meteor projects in the ~/Projects directory and its subdirectories and remove only those packages that aren’t used in your projects.
I have, but I think the preferred solution for the Meteor tool is to remove packages automatically, depending on how frequently they are used. Ideally, the cache would always have a reasonable size and you wouldn’t have to run a command manually every once in a while.
There was a bug in the initial release that could lead to the removal of the currently used meteor-tool package. In this case, you would get the error message '[...]/.meteor' exists, but '[...]/.meteor/meteor' is not executable. when running meteor. The bug is fixed in version 1.0.1 but you have to reinstall Meteor with curl https://install.meteor.com/ | sh.
To update to the latest meteor-cleaner version, run meteor npm install -g meteor-cleaner.