Meteorite is a Meteor version manager and package manager. It provides an easy way to run different versions of meteor, use non-core packages, and to install packages from the Atmosphere package repository. Meteorite provides the
mrt command that wraps the
meteor command, and should be used in its place.
# Create an app based on Meteor's devel branch.$ mrt create my-app --branch devel$ cd my-app# Install an Atmosphere package, recursively fetching dependencies.$ mrt add router# Check for and install any updates, and run the app.$ mrt
Meteorite can be installed via npm.
$ sudo npm install -g meteorite-freebsd
Meteor is not officially supported on windows; you can run it thanks to Tom Wijman's excellent work. However, meteorite's git based approach runs counter to the MSI installation that's required to get it working. So meteorite does not work under windows right now. Pull Requests which change this would be gladly accepted!
You'll also need to ensure you have git installed and available in your path.
meteor create, but you can specify the desired branch, tag or reference of Meteor's git repository that the app should be based on.
# By default, apps are based on Meteor's master branch.$ mrt create cool-app# You can create apps based on a branch of Meteor's repo.$ mrt create risky-app --branch devel# Or, on a tag (such as version numbers).$ mrt create safe-app --tag v0.5.4# Or, or on a commit.$ mrt create choosy-app --ref a9a717
meteor add, but if the package isn't one of Meteor's included packages, it installs it from Atmosphere.
meteor add, only one package can be added at a time with
# Add the latest version of the moment package on Atmosphere.$ mrt add moment# Add a specific version of a package.$ mrt add router --version 0.3.4# Meteorite will install page.js too, because router depends on it.
meteor run, but checks and installs the app's desired Meteor version and package dependencies before running the app.
Installs any available updates to the app's desired Meteor version and packages.
When Meteorite is executed for an app, it checks or installs the app's desired Meteor version, packages and dependencies, then does the required book-keeping (described below), and finally passes the command onto
For that reason, it's usually best to use
mrt for all meteor related commands. For instance, to generate the correct bundle, you'll need to use
mrt bundle, or
mrt deploy when deploying to meteor.com.
Apps tell Meteorite the Meteor version and packages they want with a file called
smart.json in their root directory. Meteorite will install those dependencies the next time it is executed within that app.
Meteorite writes to a
smart.lock file in the app's root directory to track the exact versions of its dependencies, even when it's set up in a fresh environment. You should check the
smart.lock file into your app's version control, to ensure that other developers are running the same versions of the dependencies. Any changes in
smart.json take precendency over
smart.lock file is reset with the
mrt update command.
meteor property is not required: apps will depend on Meteor's master branch by default. You can specify
meteor.git to use alternate branches, tags and forks respectively.
Meteorite packages include a
smart.json file in their root directory to provide information about the package, and to list their dependencies. For an example, see Meteor Router's
Meteorite packages also include a
package.js file in their root directory to tell Meteorite how it should be installed. For an example, see Meteor Roles'
See Atmosphere's documentation on writing packages for more information.
Contributions to meteorite are very welcome! Please see the Contribution Guide for details.