@hyperaide/cli

CLI for Hyperaide developer apps.

Install

pnpm add -D @hyperaide/cli

Commands

hyperaide login
hyperaide logout
hyperaide apps create --name "My App"
hyperaide apps link --slug my-app
hyperaide apps deploy

hyperaide apps create writes hyperaide.app.ts and, when run in an empty directory, also scaffolds a starter Vite + Hono Cloudflare Worker app. The starter uses Tailwind v4 plus @hyperaide/ui so the app can inherit Hyperaide styling and theme behavior out of the box. Use --no-scaffold if you only want the manifest and app record.

hyperaide apps link --slug ... writes hyperaide.app.ts for an app that already exists in Hyperaide. Use it when the app record exists but the current directory is not yet linked to it.

Config

Create a hyperaide.app.ts file:

import { defineApp } from "@hyperaide/cli/config";

export default defineApp({
  id: "app_id",
  slug: "my-app",
  name: "My App",
  framework: "cloudflare-worker",
  build: {
    command: "npm run build",
    outputDir: "dist",
    entry: "worker/index.js",
    assetsDir: "client",
  },
  database: {
    entities: [],
    links: [],
  },
});

Deploy model

hyperaide apps deploy builds your app locally, uploads the build artifact, and the Hyperaide backend publishes that Cloudflare Worker bundle into Workers for Platforms. The deploy archive is expected to contain the configured worker entry file plus the configured static assets directory inside build.outputDir.

Before the local build runs, Hyperaide injects:

• VITE_HYPERAIDE_DATABASE_APP_ID
• VITE_HYPERAIDE_DATABASE_TOKEN

Use those in client code when initializing @hyperaide/db.

Hyperaide app deploys now require Workers for Platforms to be configured.