Expo web previews on every PR. No CI config.

Push a branch, get a live HTTPS URL with your Expo web build running. No EAS Build waits, no CI workflow files, no manual deploy to Vercel or Netlify. PreviewDrop auto-detects Expo, builds npx expo export:web, and serves the result behind a TLS-terminated subdomain — all from your existing repo.

How PreviewDrop compares for Expo

What Expo devs deal with today

What the build needs to do

You don't write this. PreviewDrop detects Expo from your repo and builds the container for you — a Dockerfile in your repo is not used. The reference below shows the steps a working Expo web image needs: install dependencies, run npx expo export:web, and serve the resulting static files. If detection gets one wrong, set the matching Install, Build or Start command in Project Settings. Your app must listen on $PORT.

Reference (not read by PreviewDrop)
FROM node:20-slim
WORKDIR /app
COPY package.json package-lock.json* yarn.lock* pnpm-lock.yaml* ./
RUN if [ -f yarn.lock ]; then yarn install --frozen-lockfile; \
    elif [ -f pnpm-lock.yaml ]; then npm install -g pnpm && pnpm install --frozen-lockfile; \
    else npm ci; fi
COPY . .
RUN npx expo export:web
EXPOSE 3000
CMD ["sh", "-c", "npx serve dist -l ${PORT:-3000}"]

How it works