Skip to main content
The expo install command installs npm packages with versions that are compatible with your Expo SDK version. It ensures that all installed packages work together correctly.

​
Usage

npx expo install <packages...> [options]
The command is also aliased as expo add: 
npx expo add <packages...> [options]

​
Arguments

​
packages
string[]
One or more package names to install. Separate multiple packages with spaces.

​
Options

​
--check
boolean
Check which installed packages need to be updated. Shows packages with incompatible versions.
​
--fix
boolean
Automatically update any invalid package versions to compatible versions.
​
--dev
boolean
Save the dependencies as devDependencies instead of dependencies.
​
--npm
boolean
Use npm to install dependencies. Default when package-lock.json exists.
​
--yarn
boolean
Use Yarn to install dependencies. Default when yarn.lock exists.
​
--pnpm
boolean
Use pnpm to install dependencies. Default when pnpm-lock.yaml exists.
​
--bun
boolean
Use bun to install dependencies. Default when bun.lock or bun.lockb exists.
​
--json
boolean
Output dependency information in JSON format. Use with --check flag.

​
Why Use expo install?

​
Version Compatibility

Expo SDK versions require specific versions of certain packages. Using expo install ensures you get compatible versions automatically. For example, if you’re on Expo SDK 51:
  • react-native must be version 0.74.x
  • react must be version 18.2.0
  • react-dom must be version 18.2.0
Running expo install react-native installs the correct version for your SDK.

​
How It Differs from npm/yarn/pnpm

Featurenpm/yarn/pnpmexpo install
Version resolutionLatest or specifiedSDK-compatible
Compatibility check✗✓
Expo packagesManual version lookupAutomatic
Native modulesMay be incompatibleGuaranteed compatible

​
Examples

​
Install Single Package

Install a package with compatible version: 
npx expo install react-native-maps

​
Install Multiple Packages

Install several packages at once: 
npx expo install expo-camera expo-location expo-permissions

​
Install as Dev Dependencies

Install packages as devDependencies: 
npx expo install --dev @types/react typescript

​
Check for Updates

Check which packages need updating: 
npx expo install --check
Output example: 
Checking installed packages...

Found outdated dependencies:
  react-native: installed 0.73.0, expected 0.74.0
  expo: installed 50.0.0, expected 51.0.0

Run 'npx expo install --fix' to update them.

​
Fix Incompatible Versions

Automatically update incompatible packages: 
npx expo install --fix
This updates all packages to their SDK-compatible versions.

​
JSON Output

Get machine-readable output: 
npx expo install --check --json
Useful for CI/CD scripts and automation.

​
Specify Package Manager

Use a specific package manager: 
npx expo install --npm react-native-gesture-handler

​
Pass Additional Arguments

Pass arguments to the underlying package manager: 
npx expo install react -- --verbose
This runs: 
yarn add react --verbose
Or with npm: 
npm install react --verbose

​
Common Use Cases

​
After Upgrading Expo SDK

After upgrading to a new SDK version, fix all dependencies: 
npx expo install --fix

​
Adding New Features

When adding packages with native code: 
npx expo install expo-image-picker
This ensures the version works with your current SDK.

​
Setting Up New Project

Install common dependencies: 
npx expo install react-native-gesture-handler react-native-reanimated react-native-screens

​
Development Dependencies

Add TypeScript and types: 
npx expo install --dev typescript @types/react @types/react-native

​
Package Manager Detection

Expo CLI automatically detects your package manager based on lock files:
Lock FilePackage Manager
package-lock.jsonnpm
yarn.lockyarn
pnpm-lock.yamlpnpm
bun.lockb or bun.lockbun
You can override this with the package manager flags.

​
Version Resolution

​
How Versions Are Determined

  1. Check SDK Version - Reads expo package version
  2. Query API - Fetches compatible versions from Expo API
  3. Resolve Version - Determines the correct version for each package
  4. Install - Runs package manager with resolved versions

​
Expo Packages

For packages in the expo-* namespace:
  • Version matches your Expo SDK (e.g., SDK 51 → expo-camera 15.0.x)
  • Always compatible with your SDK

​
Third-Party Packages

For packages like react-native-*:
  • Versions are tested and verified by Expo
  • May differ from the latest npm version
  • Guaranteed to work with your SDK

​
Latest Versions

For packages without SDK requirements:
  • Installs the latest version from npm
  • Same behavior as npm install

​
Checking Compatibility

​
Before Installation

Check if a package is compatible: 
npx expo install --check <package-name>

​
After Installation

Verify all packages are compatible: 
npx expo install --check

​
In CI/CD

Add a check step to your pipeline: 
npx expo install --check --json
Exit code will be non-zero if packages are incompatible.

​
Troubleshooting

​
Peer Dependency Warnings

Expo install resolves peer dependencies automatically. If you see warnings: 
npx expo install --fix

​
Version Conflicts

If manual version is specified in package.json: 
{
  "dependencies": {
    "react-native": "^0.73.0"
  }
}
expo install --fix will update to the compatible version.

​
Package Not Found

If a package isn’t in the Expo compatibility list:
  • It will install the latest version from npm
  • May require manual version management
  • Check package documentation for React Native compatibility

​
Network Issues

If the API request fails:
  • Falls back to latest versions
  • Use --npm with specific version: npm install package@version
  • Check internet connection

​
Best Practices

​
Always Use expo install for Expo Packages

# Good
npx expo install expo-camera

# Avoid
npm install expo-camera

​
Use for React Native Core Packages

# Good
npx expo install react-native

# Avoid
npm install react-native

​
Check Before Upgrading SDK

# After updating expo version
npx expo install --check
npx expo install --fix

​
In Version Control

Commit lock files to ensure consistency:
  • package-lock.json (npm)
  • yarn.lock (yarn)
  • pnpm-lock.yaml (pnpm)
  • bun.lockb (bun)

​
CI/CD Integration

​
GitHub Actions Example

- name: Install dependencies
  run: npm install

- name: Check package compatibility
  run: npx expo install --check

- name: Fix incompatible packages
  run: npx expo install --fix

​
Pre-commit Hook

Add to .husky/pre-commit: 
#!/bin/sh
npx expo install --check || {
  echo "Package versions are incompatible with Expo SDK"
  echo "Run: npx expo install --fix"
  exit 1
}

​
Additional Resources

  • Compatible versions are maintained in the Expo SDK reference
  • Version API endpoint: https://exp.host/--/api/v2/versions
  • Report compatibility issues on GitHub