Skip to main content
The meteor add command adds one or more packages to your Meteor project.

Usage

Basic Usage

Add a single package:
Add multiple packages:

Version Constraints

You can specify version constraints when adding packages.

Minimum Version

Add a package at version 1.1.0 or higher (but not 2.0.0 or higher):

Exact Version

Add a package at exactly version 1.1.0:

Multiple Constraints

You can combine constraints using || (OR):
This means either 1.0.0 (exactly) or 2.0.1 (exactly). Note: Use quotes when your constraint includes spaces or special characters.

Removing Version Constraints

To remove a version constraint for a specific package, run meteor add again without specifying a version:

Options

--allow-incompatible-update
boolean
default:"false"
Allow packages in your project to be upgraded or downgraded to versions that are potentially incompatible with the current versions, if required to satisfy all package version constraints.

Examples

Add React:
Add MongoDB packages:
Add a package with a minimum version:
Add a package with an exact version:
Add a package with complex constraints:
Add a package allowing incompatible updates:

Common Packages

Authentication

UI Frameworks

Utilities

Development

Warning: Never use insecure or autopublish in production.

Finding Packages

Search for available packages:
View package information:
List packages in your project:

Package Sources

Packages can come from:
  1. Meteor Package Server - Official and community packages
  2. Local packages - Packages in your project’s packages/ directory
  3. Atmosphere - Legacy package repository (now integrated)

Version Resolution

When you add a package, Meteor’s constraint solver:
  1. Resolves all dependencies
  2. Ensures version compatibility
  3. Selects the newest compatible version of each package
  4. Updates .meteor/versions file
If the constraint solver can’t find compatible versions, it will report which packages are causing conflicts.

Troubleshooting

If you encounter version conflicts: