为何需全局安装expo-cli？转本地依赖有何损失？

Great question—this is a super common pain point for developers who value keeping dependencies scoped to individual projects, aligned with npm's core design principles. Let’s break this down clearly:

1. The real reasons Expo recommends global installation initially #

• Simplified onboarding for new developers: Global installation lets you run expo init anywhere on your machine without first setting up a project directory or package.json. This lowers the barrier to entry for beginners who just want to get a project up and running quickly.
• Historical context: Early versions of Expo CLI were designed as a global utility for managing multiple Expo projects—handling initialization, SDK updates, and cross-project workflows. Global installation made sense for that use case at the time.

2. What you gain (and lose) by using a local expo-cli dependency #

No core functionality loss #

All the critical commands you rely on—expo start, expo build, expo publish—work perfectly with a local installation. You just need to call them via:

• npx expo [command] (which automatically uses the local version in your project’s node_modules)
• Or by adding scripts to your package.json, like:

  "scripts": {
    "start": "expo start",
    "build": "expo build:android"
  }
  

Clear advantages of local installation #

• Version alignment per project: As you noted, different expo-cli versions have varying features and configuration requirements (like differences in app.config.ts validation). Local installation ensures each project uses the exact version it was built with, eliminating the risk of breaking old projects when you update your global CLI.
• Follows npm’s design philosophy: Keeping expo-cli as a project dependency keeps your setup self-contained—anyone cloning your repo just needs to run npm install to get the exact tools needed, no extra global setup steps.

Minor inconveniences #

• Initial project setup is slightly more manual: Instead of running expo init directly, you’ll need to create a directory, run npm init -y, install expo-cli locally, then initialize the project with npx expo init. That said, Expo’s newer create-expo-app tool lets you bypass this entirely with npx create-expo-app—no global installation required.

3. Why the official docs don’t emphasize the local option #

• Prioritizing simplicity for beginners: The docs’ primary goal is to get new developers up and running with minimal friction. Global installation is the most straightforward "one command" setup, so it’s highlighted first.
• Historical inertia: Early docs standardized on global installation, and while the tooling now supports local setups well, the docs haven’t shifted focus to highlight this as a primary option (though they do mention using npx for certain workflows).

It’s worth noting that Expo’s modern tooling is moving away from strict global dependency requirements—create-expo-app is now the recommended way to start projects, and it’s designed to work seamlessly with npx (no global install needed) if you prefer that approach.

内容的提问来源于stack exchange，提问作者Ilya Semenov