This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Learn how to deploy web builds to EAS Hosting alongside Android and iOS releases to existing EAS Workflows.

Our workflows from previous chapters cover Android and iOS. Let's extend them to also deploy the web build to EAS Hosting alongside the same release.

Learning outcomes

• Configure the Expo project to export a static web build
• Add a web deployment job to preview.yml to generate a non-production web build
• Add a web deployment job to production.yml to generate a production web build

EAS Hosting and the deploy job

EAS Hosting is a service for hosting and deploying web builds of an Expo app. Each deployment gets its own unique URL, and a project has a single production URL that serves whatever we last deployed to production.

The deploy pre-packaged job in EAS Workflows runs the web export, uploads the output of the export step to EAS Hosting, and returns the deployment URL as the job output. The deploy job has two parameters:

Configure web.output for static export

Before we add web deployment jobs to our workflows, we need to configure our Expo project to export a static web build. In app.json, set the web.output field to static:

{
  "expo": {
    %%placeholder-start%%... %%placeholder-end%%
    "web": {
      "output": "static"
    }
  }
}

static tells the Expo CLI to produce a directory of static HTML, JavaScript, and asset files that EAS Hosting can serve. Expo also supports single and server output; static produces plain files that any host can serve, which is all we need here.

After updating the app.json with the above configuration, commit the change and push it to the repository's main branch.

Add a web preview deployment

Setting prod: true is the difference between a preview deployment and a production deployment. Previews get unique per-deployment URLs. We created a preview workflow in Chapter 3 Step 1. Let's add a deploy_web job to that workflow so any time we create a new preview build, we also get a new web deployment.

name: Preview builds

jobs:
  # ... existing fingerprint, get-build, build_android, build_ios, notify jobs

  deploy_web:
    name: Deploy web (preview)
    type: deploy

3

Test the workflow

Now, manually run the preview workflow using the following command:

Terminal

Copy

- eas workflow:run .eas/workflows/preview.yml

On the EAS dashboard, the preview workflow run shows the deploy_web job alongside the build jobs.

Under Deploy web (preview), click the View Deployment link to open the deployed web build in the browser.

Add a web production deployment

The production workflow from Chapter 6, Step 1 runs when we push a new Git tag, and it builds or updates the native app. Let's add a deploy_web job to that workflow so that releasing a new version of the app also updates the web version on the production URL.

name: Deploy to production

on:
  push:
    tags: ['v*.*.*']

jobs:
  # ... existing fingerprint, get-build, build, update jobs ...

  deploy_web:
    name: Deploy web (production)
    type: deploy
    params:
      prod: true

Summary

Learn about the next steps to use EAS Workflows.