Installation

Requirements

• Node.js 22.12 or newer
• pnpm, npm, or Bun
• Expo Go for physical-device testing

Run the latest published CLI without installing it globally:

npx create-expojet@latest my-app

Or use pnpm:

pnpm create expojet my-app

Use a reviewed release

Keep @latest when trying the newest generator. For a team baseline, select the exact release your team has reviewed:

npx create-expojet@0.8.0 my-app

Replace 0.8.0 with your approved version and record it in your team's setup instructions. This pins the generator release, not every app dependency: generated dependency ranges are resolved when the package manager installs them. Commit the generated project's lockfile and use frozen-lockfile installs in CI to reuse that resolution.

Interactive choices

Expojet asks for the project structure, package manager, authentication adapter, styling adapter, onboarding, and EAS profiles. Stable authentication choices include Clerk, Supabase, Firebase, and none. Better Auth appears only when the CLI is started with --experimental.

Non-interactive generation

npx create-expojet@latest my-app --yes \
  --structure monorepo \
  --package-manager pnpm \
  --auth clerk \
  --style uniwind \
  --onboarding \
  --eas

Use --dry-run to validate and list the file plan without creating the target.

Local tarball testing

Contributors can test the exact publish artifact:

pnpm smoke:pack
pnpm --filter create-expojet pack --pack-destination .artifacts
pnpm dlx .artifacts/create-expojet-0.6.2.tgz create