Build
Production builds and deployment preparation
Overview
The Vite plugin prepares your project for deployment when running your build command.
Building Your Project
Run your standard Vite build command:
bun run buildnpm run buildpnpm run buildyarn run buildThe plugin automatically generates the manifest required for deployment.
$ bun run build[Playcademy]playcademy.manifest.json 0.25 kBIf auto-zip is enabled:
$ bun run build[Playcademy]playcademy.manifest.json 0.25 kB.playcademy/my-project.zip 1,234.56 kBBuild Output
Typical structure:
The Manifest
The plugin generates playcademy.manifest.json in your build output:
{
"version": "1",
"platform": "web",
"createdAt": "2025-10-09T08:30:00.000Z"
}Build Metadata
The manifest provides build metadata. Vite builds are always platform web.
Project metadata (name, emoji, backend routes) is handled by the CLI during deployment.
Manifest Fields
| Field | Value | Description |
|---|---|---|
version | "1" | Manifest schema version |
platform | "web" | Always web for Vite |
createdAt | (timestamp) | Build timestamp |
Auto-Zip
By default, the plugin creates a deployment archive at .playcademy/<project-name>.zip with all build output.
To disable automatic zip creation:
playcademy({
export: {
autoZip: false,
},
})Deployment Workflow
The typical workflow:
bun run buildplaycademy deploynpm run buildplaycademy deploypnpm run buildplaycademy deployyarn run buildplaycademy deployBuild First
The CLI doesn't automatically build your project. Always run your build command before deploying.
What happens during deployment?
The CLI reads your built dist/ directory and:
- Deploys your project to Playcademy
- Bundles and deploys any backend integrations (if needed)
- Updates project metadata from
playcademy.config.js
See Deployment Guide for details.