The meteor is still in preliminary condition. Thus, the idea of packages (still in this post) is not officially supported, although it will be soon. The meteor community has stepped in to create its own way of using third-party packages, and this is what the meteorite does.
Most of the commands you give to the meteorite are ultimately passed to the meteorite, so you see the same result.
The only (main difference) is mrt add , which first checks the js.com atmosphere for packages.
These two will be merged very soon (there is a branch on the meteor on github, called packaging, which aims to achieve this)
The idea of "clean" does not actually exist in the meteor, because most of the material is based on reloading the hot code, so when the file changes it is completely uploaded / (cleared) and rewritable.
If you change the code bit, it will restore all this if you do not have a syntax error.
However, if you want to "clear" the assembly of everything that you would need to do in two stages (meteor part and meteorite part)
This erases some things in the hidden .meteor folder
meteor reset
Delete everything in ~/.meteorite/packages
Delete all symbolic links only in your /packages projects. Be careful not to delete folders, because they will be placed by you / whoever you make your project and would not be from the atmosphere or meteor
Then run mrt update to reinstall all packages from scratch from scratch.
source share