I just cloned a repo of meteor code and cded into it. Then I installed meteorite and gave it a try. This is what I see.
$ mrt --help
Stand back while Meteorite does its thing
✓ router
tag: https://github.com/tmeasday/meteor-router.git#v0.5.4.1
✓ accounts-ui-bootstrap-dropdown
tag: https://github.com/erobit/meteor-accounts-ui-bootstrap-dropdown.git#v0.6.5.1
✓ page-js-ie-support
tag: https://github.com/tmeasday/meteor-page-js-ie-support.git#v1.3.5
✓ HTML5-History-API
tag: https://github.com/tmeasday/meteor-HTML5-History-API.git#v4.0.0
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
Usage: meteor [--version] [--help] <command> [<args>]
With no arguments, 'meteor' runs the project in the current
directory in local development mode. You can run it from the root
directory of the project or from any subdirectory.
Use 'meteor create <name>' to create a new Meteor project.
Commands:
run [default] Run this project in local development mode
create Create a new project
update Upgrade to the latest version of Meteor
add Add a package to this project
remove Remove a package from this project
list List available packages
bundle Pack this project up into a tarball
mongo Connect to the Mongo database for the specified site
deploy Deploy this project to Meteor
logs Show logs for specified site
reset Reset the project state. Erases the local database.
See 'meteor help <command>' for details on a command.
That was not very useful for --help to install smart packages. Maybe consider add special case for this option?
It does this because potentially it has to use a specific version of Meteor you've specified in your smart.json. Probably it could be a little smarter about it, but it's probably no big deal.
I just cloned a repo of meteor code and
cd
ed into it. Then I installed meteorite and gave it a try. This is what I see.That was not very useful for
--help
to install smart packages. Maybe consider add special case for this option?