The following steps assume:

• Ionify writes build output to dist/ by default (override via ionify build --out-dir <dir>)
• Ionify is installed as a dev dependency and exposed through npm scripts (use pnpm/yarn equivalents)

{
  "scripts": {
    "dev": "ionify dev",
    "build": "ionify build"
  }
}

Ionify keeps a persistent dependency graph and CAS under .ionify/cas/<versionHash>/.... Those caches are local; deployment only needs the build output.

Build the app

npm run build

The production assets are emitted to dist/. Deploy that folder to your static hosting provider of choice.