expo-dependency-check

Validate Expo project dependencies and optionally update incompatible versions via expo install --check/--fix.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill expo-dependency-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-dependency-check
Source: https://github.com/pabloimrik17/monolab/tree/main/claude-plugins/expo-developer/skills/expo-dependency-check
Command: npx skills add https://github.com/pabloimrik17/monolab --skill expo-dependency-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and resolve incompatible or broken Expo dependencies that can occur after editing package.json, preventing runtime errors and build failures in Expo and React Native projects.

Core Features & Use Cases

  • Project Detection: Checks for expo in package.json and presence of Expo config files to determine applicability.
  • Package Manager Selection: Chooses the correct command prefix by inspecting lock files such as bun.lock, pnpm-lock.yaml, yarn.lock, or package-lock.json.
  • Check and Auto-fix: Offers a check-only mode to report incompatible versions and an auto-fix mode that runs expo install to update packages to compatible versions.
  • Use Case: After upgrading a library in package.json, run this Skill to verify compatibility with the installed Expo SDK and automatically align package versions.

Quick Start

Check and auto-fix incompatible Expo dependencies after I updated package.json.

Frequently Asked Questions about expo-dependency-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Expo dependencies for compatibility after editing package.json?

To check Expo dependencies, run a package-manager-prefixed command like `expo install --check` to report incompatible versions against the installed Expo SDK. This validates dependencies after manual package.json modifications.

How do I fix incompatible Expo package versions in a React Native project?

Fix incompatible Expo package versions by running `expo install --fix` with the correct package manager prefix. This updates packages to compatible versions while preserving other project files.

How does a dependency checker detect the correct package manager for an Expo project?

A dependency checker detects the package manager by inspecting lock files in the project directory, such as bun.lock, pnpm-lock.yaml, yarn.lock, or package-lock.json, and uses the matching command prefix.

Can I use an automated dependency check for any React Native project?

Automated dependency checks apply only to Expo and React Native projects that include expo in package.json or have Expo config files present, ensuring the project uses the Expo SDK before running validation.

Why does upgrading a library in package.json cause Expo runtime errors?

Upgrading a library in package.json causes Expo runtime errors when the new version is incompatible with the installed Expo SDK. Validating dependencies with an install check aligns package versions and prevents build failures.

What's the best way to verify package compatibility without modifying other project files?

The best way to verify package compatibility without modifying other files is running a check-only mode using `expo install --check`, which reports incompatible versions while preserving the rest of the project.