meteor run Run a meteor development server in the current project. Searches upward from the current directory for the root directory of a Meteor project. Whenever you change any of the application's source files, the changes are automatically detected and applied to the running application. You can use the application by pointing your web browser at localhost:3000. No Internet connection is required. This is the default command. Simply running meteor is the same as meteor run. To pass additiona

meteor shell When meteor shell is executed in an application directory where a server is already running, it connects to the server and starts an interactive shell for evaluating server-side code. Multiple shells can be attached to the same server. If no server is currently available, meteor shell will keep trying to connect until it succeeds. Exiting the shell does not terminate the server. If the server restarts because a change was made in server code, or a fatal exception was encountered, t

meteor reset Reset the current project to a fresh state. Removes the local mongo database. This deletes your data! Make sure you do not have any information you care about in your local mongo database by running meteor mongo. From the mongo shell, use show collections and db.collection.find() to inspect your data. For now, you can not run this while a development server is running. Quit all running meteor applications before running this.

meteor publish-release Publishes a release of Meteor. Takes in a JSON configuration file. Meteor releases are divided into tracks. While only MDG members can publish to the default Meteor track, anyone can create a track of their own and publish to it. Running meteor update without specifying the --release option will not cause the user to switch tracks. To publish to a release track for the first time, use the --create-track flag. The JSON configuration file must contain the name of the releas

meteor remove package Removes a package previously added to your Meteor project. For a list of the packages that your application is currently using, run meteor list. This removes the package entirely. To continue using the package, but remove its version constraint, use meteor add. Meteor does not downgrade transitive dependencies unless it's necessary. This means that if running meteor add A upgrades A's parent package X to a new version, your project will continue to use X at the new versio

meteor publish Publishes your package. To publish, you must cd into the package directory, log in with your Meteor Developer Account and run meteor publish. By convention, published package names must begin with the maintainer's Meteor Developer Account username and a colon, like so: iron:router. To publish a package for the first time, use meteor publish --create. Sometimes packages may contain binary code specific to an architecture (for example, they may use an npm package). In that case, ru

meteor publish-for-arch Publishes a build of an existing package version from a different architecture. Some packages contain code specific to an architecture. Running publish by itself, will upload the build to the architecture that you were using to publish. You need to run publish-for-arch from a different architecture to upload a different build. For example, let's say you published name:cool-binary-blob from a Mac. If you want people to be able to use cool-binary-blob from Linux, you shoul

meteor mongo Open a MongoDB shell on your local development database, so that you can view or manipulate it directly. For now, you must already have your application running locally with meteor run. This will be easier in the future.

meteor list Lists all the packages that you have added to your project. For each package, lists the version that you are using. Lets you know if a newer version of that package is available.

meteor lint Run through the whole build process for the app and run all linters the app uses. Outputs all build errors or linting warnings to the standard output.